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

Annotations already cover the safety profile (readOnly, idempotent, openWorld), and the description adds substantial context on top: flat pricing, the 12-item cap on this door, the 25-item HTTP door, the guarantee that every item is answered by the same door as a single call (consistency), and an auditable Ed25519-signed receipt checkable offline. That is exactly the extra behavioral detail annotations cannot express.

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?

It is a single dense paragraph but front-loads purpose and forms before pricing and receipt details, and every sentence carries information (forms, limits, pricing, sibling routing, receipt). The pricing and door-detail sentences are the heaviest, but they justify their place for a paid tool.

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?

There is no output schema, so the description carries that burden; it does describe what comes back (verdicts plus an Ed25519-signed receipt covering question, verdict, sources and time) and how to verify it. Adequate for the tool's complexity, though a fuller picture of the per-item verdict shape would make it airtight.

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 100%, so the baseline is 3. The description goes slightly beyond by explaining the two forms as a semantic choice ('items[] of {tool, input} or the citations[]/packages[] shorthand') and by reinforcing the item limit, giving the agent a reason to pick one form over the other.

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 opening clause gives a specific verb and resource ('Check a whole list in one call: a bibliography or a dependency manifest') and immediately names the alternatives it is not ('to check the claims inside a document, use check_document, and to check one reference use verify_citation or verify_package'). An agent can distinguish it from every sibling without opening a schema.

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 states explicitly when to reach for this tool (a whole list / manifest in one call) and routes to the correct siblings for the two adjacent cases (prose claims → check_document, single reference → verify_citation/verify_package). Exclusions and alternatives are both spelled out, leaving nothing to inference.

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