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

Annotations already declare read-only, idempotent, non-destructive behavior, and the description adds valuable context beyond that: only verified public apps are returned, pending/expired/moderated listings are excluded, and private contacts or verification tokens are not exposed. It does not describe not-found behavior or return shape, but no output schema exists and this is a simple lookup.

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 tightly written sentences with the core action and scope front-loaded, followed by important exclusions. No redundant or filler language.

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 read-only, single-parameter lookup with no output schema and rich annotations, the description covers scope, filtering behavior, and privacy constraints well. It could mention what happens when no matching verified app exists, but otherwise an agent has enough to call it correctly.

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 description coverage is 0% for the single required 'id' parameter, so the description must compensate. It does so by clarifying that the id may be a registration id or a slug, which is essential semantic information beyond the schema's bare string/maxLength constraint.

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?

The description states a specific verb and resource: 'Get a verified public app by registration id or slug.' This distinguishes it from sibling tools like search_apps (plural search) and register_app/verify_app (mutations/verification) without needing the 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?

Usage is implied by 'by registration id or slug', telling an agent when this tool is applicable, but there is no explicit guidance on when to use this versus search_apps or other siblings. The exclusions about pending/expired/moderated listings are about results, not tool selection.

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