get_product_card

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

No annotations are provided. The description only lists what the card includes, with no mention of permissions, side effects, rate limits, or response format. Minimal behavioral disclosure.

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?

Single short sentence; concise but lacks necessary details. Could be expanded without becoming verbose.

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 no output schema, no annotations, and undocumented parameters, the description fails to provide sufficient context for correct usage. Missing return format, parameter constraints, and behavioral notes.

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 has 0% description coverage. The description does not clarify the parameters: 'id_or_url' could be ambiguous (ID or URL?), and 'marketplace' values are unspecified. No parameter guidance beyond 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?

The description clearly states the tool returns a full product card with characteristics, description, and image URLs. It uses specific verb-resource phrasing and distinguishes from sibling tools (get_reviews for reviews, marketplace_search for 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?

Usage is implied: use when needing full product details. However, no explicit guidance on when not to use or alternatives beyond sibling tool names.

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