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

Annotations already establish read-only, idempotent, non-destructive, non-open-world behavior. The description adds important context beyond annotations: the call is free, requires no x402 payment, and returns specific archive fields.

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 key operation is front-loaded and the description is short. The payment clarification has slight redundancy ('FREE', 'no payment required', 'without payment', 'no x402 challenge', 'this tool is free'), but it remains readable.

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 simple single-record read tool with rich annotations and no output schema, the description covers the return fields and payment behavior. The main remaining gap is precise id semantics, which matters because schema documentation is absent.

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 0%, so the description must carry parameter meaning. It implies the id identifies an archived proposal via the HTTP path /archive/{id}, but it does not clarify whether this is an archive-entry id, proposal id, or required format.

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?

States a specific verb and resource: read one archived proposal. It also enumerates the entry contents (discussion ids, tally, snapshot, reopen condition), so it is distinguishable from list-oriented archive tools and general proposal tools.

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 implies this is for retrieving a single archived entry, and it clarifies payment is not required. However, it does not explicitly say when to use this instead of commons_get_proposal or commons_list_archive.

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