firestarter_product

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description's 'Read-only' statement adds little beyond annotations. However, it adds useful context about the listing_id format (lst_...) and that it can be parsed from share links, which is beyond the schema. It also clarifies the tool does not handle buying or shipping, which is helpful. No contradiction with annotations.

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 two sentences, front-loaded with the core purpose, and every clause adds value. It efficiently covers purpose, usage context, and next steps without redundancy.

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?

Given the tool's simplicity (one parameter, no output schema), the description is complete. It covers what the tool returns (full detail), how to use it, and what to do next. The only minor gap is not describing the output structure, but with no output schema, the description's list of fields (photos, description, attributes, etc.) suffices.

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% for the single parameter, so the schema already documents listing_id. The description adds value by explaining the format (lst_...) and sources (catalog search, preview, share link), which goes beyond the schema's description. This is a good enhancement.

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 shows one product in full detail, listing specific content (photos, description, attributes, price, buyability, seller trust profile). It explicitly positions it as the buyer's zoom-in after catalog search or preview, distinguishing it from siblings like firestarter_preview and firestarter_catalog_search.

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 provides explicit when-to-use guidance: after firestarter_catalog_search or firestarter_preview. It also names alternatives for next steps: firestarter_execute for buying, firestarter_shipping_estimate for shipping quotes. This clearly differentiates from siblings and gives a workflow context.

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