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

No annotations are provided, so the description carries the full behavioral burden, and it discloses nothing: not whether this is a read-only lookup, whether it requires auth or an issuer registration, whether it errors on unknown keys, or what a verdict contains. 'Verdict' hints at a read but the description never states it.

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 single fragment contains no filler, but it is drastically under-sized for a four-required-parameter lookup. Brevity here reflects missing information rather than efficient structure.

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?

A tool with four required, undocumented parameters, no annotations, no enums, and no output schema needs the description to explain key formats and return shape; instead it supplies one bracketed fragment. Nothing an agent needs in order to call it correctly is present.

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?

With 0% schema description coverage, the description must compensate and does not. It lists the four parameter names but supplies no format, allowed values, or meaning — critically, 'patch_state' could be a boolean, enum, or free string and 'surface' is entirely opaque.

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 fragment 'Verdict by {framework, version, patch_state, surface}' names a resource and its lookup key but no verb or scope, so it reads as a restatement of the tool name plus its required inputs. It gives no basis for distinguishing this from siblings like attestation_check or probe.

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?

There is no guidance on when to call this tool, when not to, or which sibling to prefer (attestation_check, probe, receipts, dispatch). The agent must guess from the name alone.

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