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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, so safety is covered. The description adds genuinely useful temporal semantics — values are relative to 'the last close' and 'since the last close' — which materially affects how results should be interpreted. It stops short of explaining aggregation, whether results are per-agent rows or totals, or anything about response shape.

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?

Two sentences with no filler; the data inventory comes first and the use case second. The first sentence is a dense enumeration of unfamiliar jargon terms, which makes it slow to parse, but nothing is redundant.

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 must convey return values, and it only gestures at them via domain jargon ('seals', 'queue and panel coverage', 'calibration totals') that an agent without in-domain grounding cannot resolve into a result shape. Combined with an absent segment parameter mention, it is adequate-but-thin for a four-parameter reporting 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%, with enums and defaults fully documented for sort, dir, and limit, so the description need not repeat them. However, the description never mentions 'segment' — the parameter whose archived-vs-current semantics are the most consequential — leaving the schema's own note to carry it 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 enumerates the data returned (graders and seals since last close, queue/panel coverage, jury seat alignment, calibration totals) but never states a verb or resource framing — it is a noun-phrase inventory rather than 'returns X for a segment.' It also gives no signal distinguishing it from siblings like get_governance_overview, list_governance_directory, or list_governance_standing, which an agent would plausibly confuse it with.

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?

One sentence supplies an implied use case: 'Use it to see who is grading now and how juries aligned.' There is no guidance on when to prefer this over the many governance siblings, and no exclusions or prerequisites beyond the implicit segment scoping.

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