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

Annotations already cover readOnly, idempotent, non-destructive, and open-world, so the safety profile is done. The description adds genuinely non-structured information: 'calibrated:false — thresholds are stated, not fitted', which tells the agent the thresholds are prescriptive rather than empirically derived, and 'honest limits' signals the document itself discloses caveats. It does not say whether the content is static or whether output is large.

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?

Two sentences: the first front-loads the resource and then enumerates contents, the second delivers the calibrated:false caveat. The enumeration is long but each item is a substantive section of the document, so little is wasted; a slightly tighter list would earn a 5.

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?

With no parameters, no output schema, and annotations covering the safety profile, the remaining burden is telling the agent what it will get and how to treat it — which the description does via the content list plus the calibration caveat. Only the output format/stability and the exact usage relationship to fact_check_claim are left out.

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 tool takes zero parameters and the schema is an empty object with additionalProperties false, so there is nothing for the description to disambiguate. Baseline 4 applies; the description correctly makes no parameter claims that could mislead.

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 immediately establishes that this returns the complete ClaimGate methodology document and enumerates its contents (coherence formula, source-class weights, verdict thresholds, verbatim-quote gate, independence rules). The retrieval verb is implicit rather than stated, and no sibling tool is named or contrasted, but the resource is unambiguous.

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 says nothing about when to call this versus the other fact_check_* tools, nor does it suggest calling it before fact_check_claim to interpret verdicts. Usage is only inferable from the content list, which is a conspicuous gap given four closely named siblings.

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