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

Annotations cover the safety profile (readOnly, non-destructive), and the description adds genuinely useful behavior: per-call credit cost, repeat-call charging (reinforcing the idempotentHint=false annotation rather than contradicting it), and an untrusted-data caveat. It does not describe return shape or pagination behavior.

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 purpose front-loaded, followed by cost and trust caveats. Nothing is repetitive, though the cost sentence is split across two clauses that could be tighter.

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 32-parameter research tool with no output schema, the description covers cost and data trust but says nothing about what a returned row contains, how paging interacts with the filters, or how results relate to the monthly/trends variants. Adequate given the fully documented schema, but not complete.

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% across all 32 parameters, so the schema already documents every filter, the sort object, and returnFields. The description adds no parameter-level meaning beyond that, which is the baseline-3 case.

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?

States a specific verb ('Research') and resource ('weekly Amazon Brand Analytics keyword metrics'), and the word 'weekly' implicitly distinguishes it from the monthly and trends siblings. It stops short of explicitly naming those alternatives, but an agent can still tell which sibling family it belongs to.

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 versus amazon_aba_research_monthly or amazon_aba_research_trends, nor any mention of prerequisites or exclusions. The only routing signal is the adjective 'weekly', which the agent must infer.

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