get_product

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states 'Get full product details' without detailing return format, error behavior, permissions, or whether it reads published or draft data. This is a minimal statement that does not reveal behavior beyond the basic operation.

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 concise and front-loaded, starting with the action and resource. The list of returned fields is informative, though the trailing 'etc.' is slightly vague and adds little value, preventing a perfect score.

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 (single required parameter, no output schema), the description is adequate but not comprehensive. It lists major return content, but without an output schema or annotations, it does not fully specify the response structure or edge cases.

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 fully documents the single required parameter 'id' with the description 'Product ID', achieving 100% coverage. The tool description does not add additional parameter-level meaning, but none is needed because the parameter is self-explanatory.

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 product details by ID, and explicitly lists the included fields (name, description, price, variations, images, attributes, SEO). This distinguishes it from sibling tools like list_products or search_products, which have different scopes.

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 phrase 'by ID' gives clear context for when to use this tool: when you have a specific product ID and need full details. It does not explicitly mention alternative tools or exclusion scenarios, but the implied usage is unambiguous for typical retrieval tasks.

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