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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds the approximate catalog size (~51) and pagination, but says nothing about empty results, ordering, or why the marketplace must be trusted. Also, 'OpenAPI: getCatalog' is an internal reference rather than behavioral context.

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?

Four short sentences with the what, the alternative, the required params and the filters, all front-loaded. The trailing OpenAPI reference is the only low-value element.

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 no output schema and low parameter coverage, the description should explain what a returned 'desk starter' actually looks like (products? ASINs? bundles?) or list which fields the filters apply to. It covers routing and required params but leaves the return shape and pagination behaviour implicit.

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 only 38% across 8 parameters, so the description should carry more weight. It mentions role, budgetBand, marketplace and locale, but leaves 'category', 'limit' and 'offset' semantics to the schema (offset/limit are only hinted by 'Paginated'), and adds no meaning beyond the enum values already present.

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 names a concrete resource ('curated desk starters (~51)') and its paginated shape, which tells an agent what it gets back. It lacks a clear verb (list/get) and the term 'desk starters' is domain jargon, but the size hint makes the scope unambiguous enough to act on.

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?

'Prefer search_desk_gear for discovery' explicitly names the sibling alternative and the condition that selects it, and 'ALWAYS pass marketplace + locale' is a hard usage rule. It stops short of saying when the curated catalog itself is the right choice over search, but the routing signal is clear.

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