get_product_detail

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

The description does not mention any side effects, permissions, or error handling. As a 'get' operation, it is implicitly read-only, but the description does not explicitly state this or any rate limits or other behaviors.

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 a single, information-dense sentence that covers scope, content, and applicability without unnecessary elaboration.

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?

It enumerates the key fields returned (description, price, stock, condition, shipping, category, seller, variants) and notes that it covers both product types, giving the agent a solid expectation of the output.

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 product parameter description explains that it accepts either a slug from search results or a full URL, providing precise guidance on the expected input format.

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 clearly states the tool's function: retrieving full details for a single Toco listing, and enumerates specific fields included. It distinguishes from sibling search tools by emphasizing 'one listing' and 'full detail'.

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?

It explicitly states the tool works for both marketplace products and classified ads, giving a clear context for when to use it. It also implies it is for single items, not batch operations.

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