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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the description adds nothing on top of them: no note on latency, autocomplete-vs-search semantics, or result behavior. Since the structured safety profile is already present, the description's silence is a real gap rather than a covered one.

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?

It is a single four-word fragment with no bloat, but the extreme brevity is under-specification rather than conciseness. Nothing is front-loaded because nothing is stated.

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?

The output schema exists, so return values need not be explained, but with two parameters and a dense set of shop_app_* siblings the description leaves the agent unable to place this tool relative to shop_app_search or shop_app_shop_typeahead. Minimal completeness for a simple read tool, but the sibling ambiguity is unresolved.

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 100% — the schema documents both `query` (required, e.g. sneakers) and `limit` (default 10, max 20). The description contributes no additional parameter meaning, so the baseline of 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?

"Shop.app search suggestions" names a resource but supplies no verb and reads as a restatement of the tool name. It does not distinguish this from the closely named sibling shop_app_shop_typeahead, nor from shop_app_search, so an agent cannot tell what uniquely this returns.

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?

There is no when-to-use statement, no precondition, and no mention of alternatives such as shop_app_search or shop_app_shop_typeahead. Usage is only inferable from the word "suggestions" — anything an agent concludes is guesswork.

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