Where the workflow shifted
OpenAI Apps SDK metadata guidance treats app name, description, icon, and display information as part of the user's pre-entry judgment.
AI tool pages should explain the audience, task, required connection, permission boundary, and first safe action before they ask readers to install or try the app.
Tool names are not outcomes
The signal matters when it changes how a team ships, reviews, or recovers work, not when it only names another tool.
Check permissions and failure
- Rewrite the first screen as audience plus job plus permission boundary plus first action
- Keep the test narrow: one low-risk task or tool entry before connecting permissions, logs, failure handling, and human takeover to production
What still needs proof
Capability-led pages leave readers unsure whether they should connect an account, upload data, or continue. Keep the original source open so the announcement, the evidence, and this site's interpretation stay separate.