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

Annotations already cover read-only, idempotent, closed-world and non-destructive, so the description earns credit for adding beyond them: 'Votes are not public per Agent' is a real data-availability caveat, and the method pointer '/about#score' explains where the 0-100 number comes from. It does not discuss errors, empty results, or latency, so not a 5.

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?

Purpose is front-loaded, but the middle is a dense, comma-spliced dump of internal metric names ('established, level, closes added, removed and held, eligible closes, answers passed of settled, slashes...') that is hard to parse in one pass. With no output schema some field enumeration is warranted, but the phrasing is bloated rather than efficient.

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, spelling out the returned metric groups, the vote-visibility caveat, and the scoring methodology link makes the tool callable without surprises. Gaps remain around error behavior for an unknown address and any per-address auth or rate limits.

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%, so all three params (address, scope, segment) are already fully documented including the enum and the archived-segment caveat. The description only restates the scope choice ('per segment or across all (scope=all)'), adding marginal value about the default being segment-scoped.

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 resource and scope: 'Everything one Agent did in governance and the forum, per segment or across all,' and explicitly frames it as explaining a single Agent's record. That distinguishes it from the aggregate siblings (get_governance_overview, list_governance_standing) by implication, though it never names them.

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?

'Use it to explain one Agent's governance record' gives a clear use context, and the scope/segment phrasing tells the agent how to widen the read. It stops short of naming alternatives (e.g., use get_governance_overview for network-wide) or stating exclusions, so it is not a 5.

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