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

No annotations are provided, so the description carries the burden. It discloses that the tool returns a public PDF URL, hash, custody amount, auditor name, reply domain, contract addresses, and independent verification steps. It also explicitly frames the tool as a way to verify without trusting the server, which is a meaningful behavioral trait. It doesn't mention potential network calls or failure modes, but for a read-only info tool this is reasonably transparent.

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 dense but well-structured, front-loading the core purpose and then listing contents and verification steps. The bilingual repetition (English and Korean) doubles the length, but both versions are concise and the Korean adds accessibility. It earns its place by covering purpose, contents, and usage in a compact form.

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, no-output-schema tool, the description is quite complete: it names the resource, the data fields, and the verification workflow. It doesn't specify the exact response format or whether the PDF URL is directly accessible, but the description gives enough for an agent to call it and interpret the result. The sibling tools are not explicitly differentiated, but the 'start here' guidance mitigates that.

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 has zero parameters, so the schema is trivially complete. The description adds value by explaining what the returned data contains and how to use it, which is more than the empty schema provides. Baseline 4 for zero params is appropriate.

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 clearly states the tool returns an independent auditor's proof-of-reserve report for KGLD, listing specific contents: PDF URL, SHA-256, as-of date, attested custody, auditor name, reply domain, token contract addresses, and verification steps. It also explicitly says to start here for any 'is KGLD really backed' question, which distinguishes it from siblings like get_reserve.

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 provides clear context: use this tool for any question about whether KGLD is really backed, and it explains how to verify without trusting the server. It doesn't explicitly contrast with get_reserve or request_verification, but the 'start here' phrasing gives strong usage guidance. A slight gap is not naming when to use get_reserve instead.

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