woocommerce_get_product

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

With no annotations provided, the description carries the full burden. It adequately discloses the return payload structure (pricing, inventory, images, categories, tags, attributes) but omits error handling (e.g., product not found), authentication requirements, or rate limiting details.

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?

Two sentences with efficient information density. However, the '[UNIFIED]' prefix appears to be metadata leakage that adds no semantic value for the agent.

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 read operation with no output schema, the description sufficiently characterizes the return data. However, with zero schema coverage on inputs, the lack of parameter documentation leaves significant gaps for a tool requiring specific identifiers.

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 0%, requiring the description to compensate. While 'by ID' implies the product_id parameter, it fails to explain the 'site' parameter (format/purpose) or the 'fields' parameter (which controls response filtering). Only one of three parameters is implicitly documented.

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?

Clearly states it retrieves detailed information about a specific WooCommerce product by ID. The 'by ID' phrasing effectively distinguishes it from sibling list operations like woocommerce_list_products, though it doesn't explicitly name the alternative.

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?

Provides no guidance on when to use this versus woocommerce_list_products (for searching) or when to utilize the optional 'fields' parameter for partial data retrieval. No prerequisites or error conditions are mentioned.

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