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

Annotations already declare readOnlyHint and openWorldHint=false, so the safety profile is covered; the description adds genuinely new behavior facts: free tier, no API key required, and output parity with search_quorums. It stops short of saying whether the sample is fixed, randomized, or rate-limited, and whether it returns exactly one quorum or a small set, which are the remaining behavioral unknowns.

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?

Three sentences, front-loaded with the free/no-key differentiator and the output-shape guarantee. The middle sentence defining the quorum data model is longer than strictly necessary but earns its place by telling an agent how to interpret support_count and viewpoint labels.

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 zero parameters and an output schema present, the description needs only to explain purpose, access model, and return parity, all of which it does. The minor omission is cardinality/randomness of the sample, which an agent might want to know before relying on it for anything beyond a shape preview.

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?

The tool takes no parameters, so there is no parameter meaning to add beyond the schema. Baseline for a zero-parameter tool is 4, and the description correctly explains what the (parameterless) call returns.

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 identifies the resource ('a recent, well-sourced quorum') and ties it explicitly to the sibling search_quorums by promising 'the exact shape search_quorums returns.' It also defines what a quorum contains (viewpoints with label, summary, support_count split into media/socials/iwitness). The only gap is that the action verb is implied rather than stated, and it never contrasts with get_quorum.

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 see the data before paying' plus 'Free, no key needed' gives a concrete selection condition: pick this over paid siblings when previewing or unauthenticated. It does not spell out when NOT to use it (e.g., when you need a specific quorum by id, which get_quorum presumably covers), but the zero-parameter, free-preview framing makes the intended role clear.

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