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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is fully covered by structured data. The description adds the return shape and the semantic note that proposals carry the parameters they would change, but says nothing about ordering guarantees, pagination, or truncation behavior for the 'top' selection.

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?

Front-loaded with the resource and fields, then cleanly segmented into When to use / Do not use / Returns. Every clause carries information; nothing is repeated from the schema 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 compensates by enumerating the return structure (total_proposals, by_state{}, top_by_approvals[] and its fields). Combined with annotations covering safety and a fully documented single parameter, an agent has everything needed to call and interpret this tool.

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 sole parameter (limit, 1-100, default 20) is fully documented in the schema. The description adds nothing about the limit parameter or what 'top' is ranked by, so it is the minimum-viable baseline.

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+resource (governance proposals) and enumerates the returned fields (id, proposer, state, approvals, expiry, proposed parameter changes). It also explicitly contrasts itself with tron_get_chain_economics and tron_list_witnesses, so an agent can distinguish it from all nearby siblings.

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 explicit 'When to use' (governance/staking questions, pending chain-parameter changes) and 'Do not use' clauses that name the two alternative tools by name. The selection condition for each alternative is stated, not inferred.

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