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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), and the description usefully adds provenance (decoded from the governor's own events) and an output-format note (amounts are base-unit integer strings). It still omits ordering, pagination, and whether empty results are possible for non-participants.

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?

A single front-loaded sentence: purpose first, then the precise event definition, then returned fields, then the amount format. Nothing is redundant with the title or annotations.

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 no output schema, the description does the right work by enumerating the returned concepts (proposal, vote, pledge mechanism, voting power, assets) and the amount encoding. Only result ordering and volume characteristics are left unspecified.

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% for the single `address` parameter, so the description must carry that weight. Saying 'for a Wanchain address' identifies what the parameter means but not its expected format (e.g. 0x-prefixed hex), which is the one detail an agent could get wrong.

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?

Names the specific resource (governance activity) and the exact scope (only governor-sent transactions and governor payouts), which separates it from the generic get_address_activity sibling by implication. It never names the sibling explicitly, so an agent must infer the boundary rather than being told it.

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 scope sentence ('every successful transaction it sent to the governor and every governor transaction that paid it') implies when the tool applies and implicitly excludes general activity, which is useful. But there is no explicit 'use X instead when Y' routing among the many get_address_* siblings.

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