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

With no annotations, the description carries the full behavioral burden. It discloses authorization requirements and mentions 'Trial/pass/x402 billing,' but it omits what the tool returns, whether it mutates state, cost/rate-limit behavior, and what 'rounds' or 'payment' actually control.

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 short and front-loads the core action before the candidate and billing details. The fragments are dense but purposeful, with no wasted prose.

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?

Given six parameters, a nested object, no annotations, no output schema, and 0% schema description coverage, the description is far too thin. It provides some candidate and billing context but leaves essential parameter and behavior details undocumented.

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 coverage is 0%, so the description must compensate for all six parameters. It partially explains the candidate-input alternatives (house_double versus target_url+authorised+authorisation), but it never explains 'rounds' or 'payment' and does not describe the shape of the house_double object.

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 verb and resource: 'Run a rewrite-regression pack against an authorised candidate.' It is clear what the tool does, but it does not explicitly distinguish itself from siblings like rewrite_verify_pack or rewrite_verdict.

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?

It gives candidate-selection guidance via '(house_double or target_url+authorised+authorisation)' and references billing modes, which implies usage context. However, it does not say when to use this tool instead of rewrite_verify_pack, rewrite_verdict, or rewrite_family.

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