Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare the mutation profile (readOnlyHint=false, destructiveHint=false, openWorldHint=true), so the safety basics are covered. The description usefully adds the ownership precondition and the dedupe note against publish_app, but says nothing about submission semantics such as whether a pending submission can be replaced, whether it locks the app, or what errors an already-submitted app produces.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences with zero filler. The action and precondition come first, followed by the alternative and the next step, so the critical routing information is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter action with no output schema and annotations covering the safety profile, the description supplies preconditions, siblings to avoid, and the polling follow-up. The only gap is the outcome of the call itself (does it queue a review, and what happens on duplicate submissions), which an agent might still need to infer.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and both parameters are documented there, including the api_key fallback rationale. The description only echoes the ownership constraint for slug ('an app you own'), adding no format or validation detail beyond the schema, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Send an app you own to review') plus the scope constraint of ownership. It also pre-empts confusion with publish_app by noting publish_app already submits, so an agent can separate the two without reading either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit sequencing ('after create_app, upload_media or update_app_html'), names the alternative that makes this tool unnecessary ('publish_app already submits'), and says what to do next ('poll get_submission_status'). When-to-use, when-not-to, and the follow-up step are all present.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.