Get Shop Product

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

No annotations are provided, so the description must carry the burden. It implicitly indicates a read-only operation and describes the return dictionary, but it does not explicitly state side-effect-free behavior, error behavior, or access requirements.

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 front-loaded with purpose and usage, followed by clearly separated Args, Returns, and Example sections. Every sentence contributes useful information with no filler.

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 one-parameter read tool, the description fully covers the use workflow, parameter provenance, and return shape. Output schema exists, so the included return fields are a bonus rather than a requirement.

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 only specifies an integer, but the description adds meaning: 'product_id: WooCommerce product ID (from list_shop_products result).' This clarifies the parameter's source and semantic role, compensating for the 0% schema description coverage.

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?

States a specific action and resource: 'Get detailed information about a specific shop product.' It clearly differentiates from list_shop_products by emphasizing 'specific' and later referencing the list step.

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?

Gives explicit workflow context: 'Use this after list_shop_products... before adding it to a checkout session.' It does not explicitly mention when not to use sibling tools like product_view or refresh_product, so it misses the full when-not guidance.

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