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

All annotations are false, so the description carries the full burden. It discloses the return states (PASS, FAIL, REVIEW), the nature of findings, repair suggestions, the determinism hash, and the re-verifiable certificate. It also states the determinism guarantee explicitly, which is beyond the annotations and provides actionable behavioral insight.

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 two sentences, front-loaded with the core verb and purpose, then enumerates outputs efficiently. Every clause adds information: timing, result set, determinism, and certificate. No fluff or repetition.

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 there is no output schema, the description fully covers the return format: verdict (PASS/FAIL/REVIEW), findings, repair suggestions, hash, and certificate. It also explains the determinism property and the re-verifiability, which is crucial because sibling tools verify_certificate and verify_replay exist. For a validation tool of this complexity, nothing essential is missing.

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 each parameter is already documented. The description adds no new semantics about api_key, blueprint, or structured_data; it repeats the fact that Blueprint rules govern validation, which the schema already implies via the blueprint description. No additional value beyond the schema.

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 ('Validate'), a precise target ('structured data against a Blueprint's rules'), and the temporal condition ('BEFORE the result is used'). It also lists the return payload, distinguishing it from sibling tools like verify_certificate or check_blueprint_health, which have different purposes.

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 description clearly implies when to use it ('BEFORE the result is used') and mentions the determinism and certificate aspects that relate to verify_certificate and verify_replay, but it does not explicitly name alternatives or state when not to use it. The context is provided but without formal exclusions.

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