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

Beyond readOnlyHint/openWorldHint, the description discloses the cost model ($0.01 per quorum, empty page free, first 100 calls in 7 days free), the authentication requirement (Quorumz API key as a Bearer token on the connection), sort order, and pagination method. These are exactly the operational facts an agent needs before calling a paid, credentialed endpoint, and none are recoverable from 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?

It is front-loaded with the feed description and closes with the two operational constraints that matter most (cost and auth). The sentence enumerating viewpoint fields overlaps with the output schema, which is a small amount of waste but doesn't obscure the call-relevant information.

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 read-only, credentialed, metered listing tool the description covers ordering, filtering, pagination, cost, and auth, and an output schema already documents return shape. An agent has everything needed to decide to call it and to call it correctly.

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 description's parameter-relevant content (country filtering, cursor paging) merely restates what the schema already documents with more precision (ISO 3166 alpha-2, next_cursor of previous page). Baseline 3 applies since the schema carries the semantic load.

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 the resource concretely ("the live quorum feed, newest first") and defines what a quorum is (a story split into viewpoints with label, summary and support_count), plus its filtering and paging capabilities. It never names its closest siblings (get_quorum, sample_quorum) or explains how it differs from them, so an agent can't fully route between the quorum-family tools from this text alone.

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?

"The live quorum feed" plus "Filter by country; page with cursor" implies a browsing/listing use case, but there is no explicit when-to-use or when-not-to guidance and no mention of sample_quorum or get_quorum as alternatives for other needs. Usage is inferable rather than stated.

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