amazon_browse

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

Annotations already declare readOnlyHint=true, idlempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered by structured data. The description adds nothing beyond that: it doesn't mention that credentials (access_key, secret_key, partner_tag) must be supplied, whether results are paginated, or what the response contains. For a tool with credential parameters this silence is a meaningful gap.

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?

The single sentence is front-loaded and free of padding, but at four parameters with no schema documentation it is drastically under-specified rather than truly concise. Brevity here is a symptom of underspecification, not economy.

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, zero schema descriptions, no output schema, and no annotations covering authentication, the description should explain how to call the tool and where to get a browse node ID. It does neither, leaving the agent to guess at required credentials and identifier sourcing.

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% across four parameters, so the description carries the full burden and fails. The required browseNodeId is never explained (what a browse node is, or how to obtain one), and the three credential parameters are entirely unmentioned. Compare to the calibration LOW case: undocumented params at 0% coverage score 1, and this tool has four of them.

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 verb ('Browse') and a resource ('Amazon product categories'), so the general purpose is inferable. But it doesn't explain what 'browse' yields versus sibling amazon_search or amazon_product, nor that the operation is scoped to a specific browseNodeId. An agent cannot tell from this sentence why it would pick this tool over amazon_search.

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 statement of when to use this tool, no prerequisites, and no reference to the obvious alternative amazon_search for keyword lookups. The only usage signal is implicit in the phrase 'browse categories,' which the agent must interpret against the sibling list on its own.

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