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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds no behavioral context whatsoever - no pagination behavior, no matching semantics, no empty-result behavior - for a tool with limit/offset parameters.

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 with no padding and no wasted words, correctly front-loaded. However, that brevity is the result of under-specification rather than efficient information packing, so it earns only a middling score.

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 six-parameter search tool with filtering (app, platform, verified), pagination (limit, offset) and no output schema, the description omits almost everything an agent needs. The annotations cover read-only safety but nothing about matching, filtering or result shape is conveyed.

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 six parameters. The phrase 'action meanings' faintly hints at the q parameter and 'app labels' at app, but platform, verified, limit and offset are entirely undocumented in both the schema and the description, so the description does not compensate for the coverage gap.

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 verb 'Search' is clear but the resource is fuzzy: 'action meanings and app labels' never says it returns keyboard shortcuts, and it does not distinguish itself from lookup_shortcut or get_app_shortcuts. An agent can guess it is a query over shortcut metadata but cannot confidently separate it from its siblings.

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 when-to-use, when-not-to-use, or alternative is named. With lookup_shortcut, get_app_shortcuts, list_apps and compare_platforms as siblings, the description gives no signal about which entry point to pick for a given query.

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