Get Product Questions

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered; the description adds real behavioral context beyond that: a 60-second cache window, the fact that included answers may be fewer than answer_count (truncation), and an explicit prompt-injection warning that Q&A content is user-authored data, not instructions.

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, front-loaded fragments that each carry information — scope, caching, sort, truncation caveat, safety note. Slightly telegraphic but no wasted sentences.

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?

An output schema exists, so return values need not be described, and the description covers caching, truncation, and the safety caveat. The remaining gap is parameter-level detail for page and product_id format, which is minor for a read-only listing tool.

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%, so the burden falls on the description, which does explain the two sort modes (newest vs most answers) and implies single-page paging via 'one native question page'. However, it never clarifies the page parameter semantics, the max of 1000, or the product_id pattern, leaving roughly half the semantics to the raw schema.

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+resource: reading one page of a product's native questions with their answers. The resource (questions) is clearly distinct from neighboring read tools like get_product_reviews, get_product_ratings, and get_product, though no sibling is named explicitly.

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?

Usage is implied — browse questions for a product, optionally sorting by newest or most answers — but there is no explicit when-to-use vs when-not, nor any routing to sibling tools such as get_product_reviews for a different content type.

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