Recently registered Aerodrome voting pools

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

Annotations already indicate read-only, idempotent, and non-destructive behavior. The description adds a useful caveat that registration order is not token listing or pool creation time, and instructs to preserve partial rows and pagination coverage—valuable beyond annotations.

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 a single sentence that front-loads the primary purpose and adds necessary caveats without excess wording. It could be more structured but is concise and clear.

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 tool with three parameters and no schema descriptions, the description must explain pagination mechanics. It fails to clarify how sinceIndex/beforeIndex work or that limit sets page size. An agent cannot reliably use the tool without guessing, despite the output schema.

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 0% and the description does not explain the meaning of sinceIndex or beforeIndex. It mentions 'bounded pages' and 'pagination coverage' but does not define cursor parameters or explicitly tie limit to page size, leaving the agent to infer from names alone.

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 verb 'browse' and the resource 'official Voter pool registrations', with specifics on ordering (newest index first) and data included (token pair metadata and gauge state). It distinguishes from siblings by focusing on the pool directory rather than positions, rewards, or wallet data.

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?

Provides clear context: this tool is for browsing bounded pages of official registrations, not general token listings. However, it does not explicitly name alternatives or state when not to use it, only implies that ordering differs from other sources.

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