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

With no annotations to carry the burden, the description discloses useful behavioral details: it requires a ChainHelix API key or per-call payment, it returns proposals, votes and scores per space, and it was built with a sorting order ('most active first') and a window bound. It does not state side effects (likely none) or exact response format, but it is far above minimum.

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 one dense paragraph and begins with payment/API details rather than the tool's main purpose, which forces an agent to scan for relevance. However, every sentence carries essential information—two for auth/payment, one for output behavior, and two for parameters—so there is no filler.

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?

In conjunction with an output schema, the description covers the core domain, but there are gaps. It does not explain how omitting `space` or setting `limit` changes results, nor whether the API key/payment options are mutually exclusive. Given no annotations and the external side-channel requirements, this rounds out to adequate but incomplete.

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 schema provides no descriptions (0% coverage), so the description must compensate. It explicitly defines 'space' with a concrete Snapshot id example and 'window' with units, default, and maximum. The only undocumented parameter is `limit`, which is fairly standard but would benefit from a note about whether it caps proposals or votes and whether it historically defaults.

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 identifies the resource (DAO governance on Snapshot) and the output content (proposals, votes, and scores per space). It lacks an explicit verb like 'list' or 'retrieve', but the behavior is unambiguous enough for an agent to differentiate it from siblings like 'open_interest' or 'prices'.

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 gives no guidance on when to choose this tool over alternatives or when not to use it. It does state preconditions (API key or payment), but it does not provide usage context such as 'use this when governance activity is needed and other tools are insufficient'.

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