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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorld, so the safety profile is fully covered structurally. The description adds genuinely useful behavioral context — the result is capped at the last 5 proposals and includes vote counts and states — but says nothing about ordering, freshness, or behavior on chains with no governance activity.

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?

Three short sentences, front-loaded with the core action and followed by output scope and chain support. Nothing is padded, though the final 'Supported' sentence is the one carrying the inaccurate chain list.

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 an output schema present, the description need not explain return values, and annotations cover the safety profile. What is missing is accuracy on chain support, which conflicts with the schema and leaves the agent unsure whether the tool works on the 40+ other enumerated chains.

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 100% and the enum is fully self-documenting, so the baseline would be 3. However, the description states 'Supported: Ethereum, Arbitrum, Optimism' while the schema enum lists 44 chains and defaults to 'base' — actively misleading parameter information that could steer an agent away from valid chains, including the default.

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 on-chain DAO governance proposals', with concrete scope ('last 5 proposals with vote counts and states'). It is unambiguous what the tool returns, though it doesn't explicitly differentiate itself from siblings (no sibling covers governance, so the risk is low).

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?

There is no explicit when-to-use or when-not-to-use guidance, and no named alternatives. The 'Read' verb and the readOnly annotation imply a read-only inspection context, but the agent must infer that on its own.

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