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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, and the description merely restates this as 'read-only, runs straight away'. It adds no context beyond the annotations – nothing about behavior when the ID does not exist, error handling, or whether unpublished products are returned.

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?

A single compact sentence with the action and scope front-loaded. The trailing 'Through Royally: read-only, runs straight away' clause is the least useful part but is brief enough not to be costly.

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 tool with full schema coverage and complete annotations, the essentials are present. However, with no output schema, the description does not say what a returned product record contains or how a missing ID is handled, leaving a small but real gap.

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 100%, so both the id and site_id parameters are fully documented with an enum and site URL in the schema. The description adds no meaning beyond 'by ID', so the baseline 3 applies.

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 verb and resource ('Get single WooCommerce product by ID'), which implicitly contrasts with the sibling list tool wc_get_products. It names the target site explicitly, though it does not name any sibling by name, so an agent must infer the list-vs-single distinction.

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 explicit statement of when to use this versus wc_get_products, wc_create_product, or wc_update_product, and no prerequisites are given. Usage is only implied by 'by ID' – the agent must infer that it needs a known product ID.

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