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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds valuable behavioral context beyond annotations: pagination costs 1 credit per page, a maximum of 5 pages per request is implied via max_page, and rating filtering can be used strategically to avoid paging through everything.

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 description is compact and front-loaded, leading with the core function, then use cases, then the alternative tool, then cost and filtering tips. Every sentence adds value, and there is no wasted repetition of the schema or annotations.

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 tool with 7 parameters and no output schema, the description covers purpose, selection criteria, alternatives, cost implications, and a useful filtering strategy. It names the key returned content (star ratings, comment text, dates), though it does not detail the exact response shape or pagination semantics beyond credit cost. Overall it is sufficient for correct invocation.

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?

The schema already covers 100% of parameters, so the baseline is 3. The description adds meaningful parameter guidance beyond the schema: it explains that rating range and time period filters exist, and specifically recommends setting max_rating to 3 to target dissatisfied customers. This directly helps the agent choose parameter values.

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 uses a specific verb ('Read') with a clear resource ('individual buyer feedback entries for an Amazon seller') and lists concrete contents: star ratings, comment text, and dates. It also distinguishes itself from get_seller_profile by framing this as the 'reputation deep-dive tool,' so the agent can differentiate it from siblings.

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?

The description states explicitly when to use the tool: when the user wants actual buyer comments, complaint-pattern analysis, or service-quality audits. It also gives a clear alternative (get_seller_profile) for aggregate scores, and adds practical guidance about credit cost per page and using max_rating=3 to find dissatisfied customers.

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