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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses the billing model ($0.01 per call, unknown ids are not charged), the authentication requirement (Quorumz API key as a Bearer token on the connection), and the free tier (first 100 calls in 7 days). These are exactly the operational facts an agent needs before spending a paid call, and nothing contradicts the annotations.

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?

The purpose is front-loaded in the first clause, followed by resource definition, then cost and auth. Every sentence carries useful signal, though the detailed viewpoint/support-count breakdown partially duplicates what the output schema already conveys.

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?

For a single-parameter read tool with full schema coverage, an output schema, and safety annotations, the description is self-sufficient: it covers semantics, cost, authentication, and free-tier limits. The only missing piece is sibling differentiation against sample_quorum and search_quorums.

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?

There is a single parameter at 100% schema description coverage, so the schema already defines quorum_id and notes it comes from another record. The description only restates "by quorum_id" without adding format, sourcing, or validity guidance. Baseline 3 applies since the schema carries the weight.

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 states a specific retrieval ("One quorum by quorum_id") and defines the resource domain richly: a news story split into distinct viewpoints with labels, summaries, and support counts split across media, socials and iwitness. An agent knows exactly what object comes back. It does not, however, distinguish this from siblings like sample_quorum or search_quorums, which are alternate routes to quorum data.

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?

Usage is only implied: "by quorum_id" signals this is the lookup path when an id is already known. There is no explicit statement of when to prefer this over search_quorums (discovery) or sample_quorum (exploration), and no exclusion criteria. The cost and free-tier notes help an agent decide whether to spend a call, but they are not routing guidance.

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