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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so safety is covered. The description adds essentially nothing beyond restating purpose—no note on pagination behavior, result ordering, or what 'recorded' implies.

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?

A single short sentence—appropriately sized and front-loaded, but so terse it omits needed detail. Concise, not poorly structured.

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?

With four parameters at 0% coverage, no output schema, and only a one-line description, the agent lacks pagination semantics, platform filtering meaning, and return format. Inadequate for the tool's actual complexity.

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 0%, so all four parameters (app, limit, offset, platform) are undocumented. The description mentions only the app resource and says nothing about limit/offset pagination or the platform filter, leaving it entirely to compensate and failing.

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?

Specific verb+resource ('Get an app's recorded shortcuts'), clearly distinguishing it from siblings like search_shortcuts or lookup_shortcut. 'Recorded' hints at stored data, though what a 'shortcut' means is not elaborated.

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?

No guidance on when to use this vs search_shortcuts or lookup_shortcut, nor any notion of prerequisites. The agent must infer usage from the name alone.

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