woo_get_coupon

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

With no annotations provided, the description carries the full behavioral burden. 'Get' implies a safe read, but it says nothing about permissions required, whether the coupon must exist or what happens if it doesn't, or the shape of the returned object.

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?

Three words, front-loaded and waste-free, but this brevity reflects under-specification rather than tight writing. There is no structure to evaluate beyond the single phrase.

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 two-parameter tool with no annotations and no output schema, the description is far too thin. It leaves the agent without return-value expectations, error behavior, or disambiguation from the many sibling coupon and product tools.

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%, and the schema documents both 'id' (Coupon ID) and 'site' (Site id, see list_sites). The description adds nothing beyond the schema, so the baseline of 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 clear verb+resource ('Get coupon details'), so the agent knows it's a read of a single coupon. However, it does nothing to distinguish itself from siblings like woo_list_coupons or woo_get_product, and the scope (single vs. list) is only implied by the singular noun.

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?

No guidance on when to use this versus woo_list_coupons (to browse) or woo_update_coupon (to modify). No mention of prerequisites, auth, or the required site/id combination. The agent must infer usage entirely from the name.

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