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

Annotations already declare readOnly, idempotent and non-destructive behavior, so the safety profile is covered. The description adds genuine behavioral context beyond them by disclosing a conditional: competitor fields (Buy Box price, offer count, weakness signal) appear only when the ASIN is a watched competitor. It stops short of describing pagination or result volume for a read-heavy tool.

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?

Content is front-loaded with the returned metrics before the usage examples, and every clause carries information. The single long sentence is dense but not padded; a small deduction for cramming three distinct ideas into one sentence chain.

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, the description carries the burden of describing returns and does so thoroughly, including the conditional competitor fields. The main gap is the absence of any note on result scope/volume for the requested window, which an agent would benefit from knowing.

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%, so the schema fully documents days, account and marketplace_id. The description adds no parameter-level detail (e.g. window semantics, default/max values) beyond what the schema already states, making the baseline 3 appropriate.

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 the specific resource (product/ASIN and category targets) and enumerates the concrete metrics returned: clicks, orders, spend, sales, measured break-even CPC against bid price, plus competitor Buy Box price, offer count and weakness signal. This clearly separates it from siblings like get_ads_targets and get_buybox_status.

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?

Three explicit example questions ('which competitor ASINs should I target', 'are my product targets profitable', 'is the competitor I target out of stock') give strong situational context. However, no alternatives or exclusions are named, so it does not reach the explicit when-not/alternative routing of a 5.

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