WooCommerce: Get product

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds genuine value by enumerating the returned data (pricing, inventory, images, categories, tags, attributes), but says nothing about failure behavior for an invalid ID, permission requirements, or whether `fields` affects the payload.

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 tight sentences, front-loaded with the action and followed by the payload summary; nothing is padded. The '[UNIFIED]' prefix is noise but costs little.

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?

Return content is described, which is appropriate since there is no output schema. However, with 0% schema coverage and a required `site` parameter plus an opaque `fields` parameter, the definition leaves real gaps an agent would need to guess at.

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% across three parameters, so the description must carry the burden and it does not: only product_id is reflected ('by ID'), while `site` (required) and especially `fields` (a projection/filter parameter with default null) are never explained. An agent cannot tell from the text what `fields` accepts or that it can trim the response.

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 uses the specific verb+resource pair 'Get detailed information about a specific WooCommerce product by ID' and states the scope is a single product identified by ID, which clearly separates it from list/create/update siblings. It stops short of naming an alternative for edge cases (e.g., SEO-specific retrieval), but the core purpose is unambiguous.

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?

There is no when-to-use guidance, no prerequisites, and no mention of when a different tool (such as the SEO variant or a list tool) would be preferred. Usage is only inferable from the phrase 'by ID', which is not real guidance.

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