wp_get_product

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

With no annotations, the description carries the burden of conveying behavior. 'Get' clearly implies a read-only fetch with no mutation, which is good, but the description does not mention error behavior, required permissions, or what exactly 'full details' includes. This is acceptable for a simple getter but not richly transparent.

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 a single, focused sentence with no filler or redundant phrasing. 'Full' adds useful scope clarification, and the structure is immediately parsable by an 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 simple one-parameter getter with no output schema, the description is reasonably complete: it names the action, resource, and scope. It could be slightly stronger by clarifying what set of fields are returned, but given the low complexity, it provides enough context for correct invocation.

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 schema already fully documents the only parameter (id with description 'Product ID'), so schema description coverage is 100%. The description adds no parameter-level meaning beyond this, so the baseline of 3 is appropriate.

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 states a specific action ('Get') and a specific resource ('full WooCommerce product details'), making it clear this is a single-item retrieval tool. It distinguishes itself from siblings like wp_list_products, wp_create_product, wp_update_product, and wp_delete_product by signaling read-only retrieval of one product's complete data.

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 description gives no explicit guidance on when to use this tool versus alternatives such as wp_list_products or wp_get_cpt_item. It does not mention prerequisites like knowing the product ID or when a product might be better fetched through another endpoint.

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