Read a Governor proposal via a hosted indexer (legacy)

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

Annotations only say readOnly and open-world; the description adds the decisive fact that the upstream service is gone, plus an implicit hint that this path may need an API key while the alternatives do not. It doesn't say what a call actually returns now (error, timeout, stale cache), which is the remaining gap.

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, zero waste, with the depreciation warning front-loaded before the redirect. Every clause carries operational value.

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 dead legacy endpoint the agent needs the deprecation notice and the exit path, both of which are present. What's missing is the failure mode on invocation and whether historical tallies are recoverable elsewhere.

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 description coverage is 100% and the schema already documents tallyId, onchainId and the governorId-alongside-onchainId constraint. The description adds no parameter guidance, so the baseline 3 applies.

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 (fetches a proposal's title, description and tallies) and pins the source (Tally-compatible hosted API). Explicitly separates it from governor_find_proposals and governor_proposal_state, so an agent can route without opening any 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?

Gives an explicit when-not (the backing API shut down in March 2026) and names two concrete alternatives with the axis to choose between them (description vs. live on-chain state). The 'prefer X for Y' mapping leaves nothing to inference.

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