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

Annotations already declare readOnlyHint=true, so the read-only claim repeats structured data. The description still adds genuinely new behavioral context: 'No auth needed' and that the call 'changes nothing and can be repeated safely' (idempotent/repeatable), plus what data the record contains. With annotations covering the safety profile, this additional context earns credit.

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?

Four short sentences, front-loaded with the core 'canonical source of truth' claim. The final READ-ONLY sentence is somewhat redundant against the readOnlyHint annotation and repeats 'no auth', but there is little waste overall.

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 zero-parameter read with no output schema, the description is the only guide to what comes back, and it lists only three content categories rather than the record's shape or fields. It is adequate to decide to call the tool, but the return payload remains underspecified.

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 with 100% schema coverage, so there is nothing for the description to disambiguate. Baseline for a no-param tool is 4.

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 precisely enumerates the resource contents — treasury address, sanctioned money-in paths, and the official token contract — and the title supplies the read verb. An agent can distinguish it from siblings like 'treasury' or 'payout_wallet' by the 'canonical source of truth' framing. It stops short of a clean verb+resource sentence in the body itself, relying on the title for the action.

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 gives explicit usage context: 'Check any "1F916 official X" claim against this, including any claim about which token is ours.' That is a concrete trigger condition. However, it does not name alternative tools or state when NOT to use this (e.g., for non-official lookups), so it falls short of a full when/when-not treatment.

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