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

The description instructs 'Burn via POST /v1/session/cert + verify', which indicates a mutating or destructive workflow, while annotations declare readOnlyHint=true and destructiveHint=false. This is a direct annotation contradiction. The phrase 'opens 7d / 500 PASS' also implies a state change, compounding the inconsistency.

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, but it reads as a stream of abbreviations and slash-separated fragments rather than a structured explanation. There is no plain-language lead sentence, and items like 'Invoice alt $299/mo' and 'UI: /challenge' are not clearly relevant to tool invocation. This brevity is under-specification, not genuine conciseness.

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 tool that appears to open a paid gateway pilot, the description leaves critical context unexplained: what the $100.00 payment does, what a 'PASS' is, what a 'DENY' means, how the burn step relates to the pilot, and what the agent should actually do. The output schema may cover return shape, but the surrounding operational context is far too incomplete.

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 input schema already documents agent_id and company with 100% coverage, so the baseline is 3. The description adds no meaningful detail about these parameters; references to pass counts, pricing, and DENY are not tied to any schema field. It neither improves nor harms parameter understanding.

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 hints that this is an alternative path that 'opens' a 7-day / 500-pass window for $100 USDC, so it is not a pure tautology. However, it never states the tool's core action and resource in plain language; phrases like 'Wealth Exact alt' and 'Exact USDC $100.00 opens 7d / 500 PASS' are cryptic. It only weakly distinguishes itself from siblings by naming sqlguard_challenge.

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 line 'Prefer sqlguard_challenge when you have a DENY' gives an explicit alternative and a condition, which is useful. But 'DENY' is undefined, and the rest of the guidance ('Invoice alt $299/mo', 'Session/Workday OFF TABLE as primary') is too elliptical to help an agent decide reliably. There is no clear summary of when to use this tool versus the sibling set.

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