get_product

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

With no annotations, the description must carry the behavioral burden. It does disclose the returned field set, the normalization behavior, and the NOT_FOUND error outcome, which is genuine context, but it never states that this is a read-only operation or what permissions are required.

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, front-loaded with the operation and scope, and the second sentence delivers the error case without padding. The field enumeration is slightly long but each item is informative rather than 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?

There is no output schema, so the description correctly compensates by naming the fields returned and the failure mode. It is nearly complete for a single-parameter read tool, missing only permission/read-only framing.

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%, with the product_id parameter fully documented including type and minimum, so the schema does the heavy lifting. The description only restates 'integer ID' and adds no format or edge-case detail beyond the schema baseline.

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 (Retrieve) and resource (WooCommerce product) and enumerates the returned data (SKU, price, sale price, stock quantity, status). It does not explicitly differentiate itself from siblings like get_order or search_products, so an agent must infer the boundary from context.

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 phrase 'by its integer ID' implicitly tells the agent this is the direct-lookup path versus the sibling search_products, but no alternative is named and no precondition is spelled out. Usage is inferable rather than stated.

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