product_get

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

The description ends with 'Read-only', which is consistent with the annotations (readOnlyHint=true, destructiveHint=false, idempotentHint=true). It adds value by detailing the returned fields (variants, variant_types, translations), providing context beyond the annotations' safety signals.

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 sentence that front-loads the main action 'Get full product details by id' and appends necessary details in parentheses. Every part is purposeful and there is no wasted text.

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?

For a simple read-only get tool with full schema coverage and no output schema, the description adequately explains what is returned (variants, variant_types, translations). It could mention that it returns a single product object, but the current completeness is sufficient.

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 input schema already describes both parameters (site and product_id) with 100% coverage. The description does not add new semantics beyond stating 'by id', which is already inferred from the schema. Baseline 3 is appropriate.

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 'Get full product details by id', specifying the action (get) and resource (product). It distinguishes from sibling tools like products_list by highlighting the included fields (variants, variant_types, translations), which are not available in a standard list response.

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 implies when to use this tool (when full details with variant info and translations are needed) but does not explicitly state when not to use it or mention alternatives like products_list for lighter data. The context is clear, though exclusions are not provided.

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