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

With no annotations provided, the description carries the full disclosure burden. It explicitly declares 'NON-WRITING,' lists absent side effects, and adds important caveats: 'a deliberate diagnostic may still be recorded' and 'accepted means mint-valid, not confirmation-ready.' This is unusually transparent for behavior beyond the schema.

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 front-loaded with the core purpose and remains dense throughout. Each sentence adds a distinct fact — side-effect absence, replication semantics, spend caution, and mint behavior — with no repetition or filler.

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 6-parameter tool with no annotations and no output schema, the description covers purpose, side effects, and caveats well. It leaves some operational details implicit, such as what a validation result looks like and how 'known_obstructions' are surfaced, but these are minor given the strong non-writing preflight framing.

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 the baseline of 3 applies. The description adds context about the operation as a whole but does not meaningfully elaborate on individual parameters; the schema already documents terms like manifest, estimand, and admissibility_gates.

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 opens with a specific verb and resource: 'validate the exact attempt pin before reader spend.' It also distinguishes itself from sibling tools by stating it 'allocates no id, opens no obligation and consumes no attempt budget,' making the preflight nature clear.

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 provides clear timing context ('before reader spend'), a caution ('Stop before confirmation spend on known_obstructions'), and a replication-specific rule ('inspect replication_preparation'). However, it does not explicitly name an alternative sibling tool to use instead, only implying the relationship with 'Mint repeats validation under lock.'

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