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

The annotations already declare destructiveHint=true, idempotentHint=false, and readOnlyHint=false, so the risk profile is partly covered. The description adds genuinely new behavioral context beyond them: the operation is potentially slow ('may take time') and requires a human confirmation gate before the mutating call. It does not explain what the repair overwrites or whether it can be safely re-run, which keeps it from a 5.

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 short sentences with zero filler. The action and resource come first, the runtime caveat second, and the confirmation prerequisite last, which is the right order for an agent to act on.

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, non-idempotent maintenance write with no output schema, the definition covers the essentials (what it does, that it is slow, that it needs confirmation). It is still incomplete on the things that matter most for a destructive operation: what data is replaced, whether the repair can be undone, and how to verify success afterwards.

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 site_id and confirm are already fully documented in the schema, including the instruction to call list_sites first. The description only echoes the confirm semantics already present in the schema and adds no new format or constraint detail; baseline 3 is correct.

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 pair: 'Repair missing discount amounts in the coupons lookup table', which is concretely different from the sibling wc_maint_regenerate_product_lookup_tables and from read tools like wc_get_coupons. It stops short of naming a sibling or explicitly contrasting, so a 4 rather than a 5.

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 definition gives one concrete usage rule: obtain explicit user confirmation before calling with confirm=true, matching the schema's requirement. It says nothing about when this repair is warranted versus alternatives such as regenerating lookup tables, nor what symptom indicates missing discount amounts, so the selection guidance is only implied.

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