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

Annotations already mark the operation as read-only, idempotent, and non-destructive. The description adds useful behavioral context beyond that: the membership is returned 'in fixed order' and the caller needs the 'comparisons:read' permission. No contradiction with 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 description is two short sentences with no filler. The action ('Read') is front-loaded, and the permission requirement is appended without bloating the text.

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 operation with strong annotations, the description covers the essential behavioral guarantees: what is read, the ordering, and the auth requirement. It does not specify return structure or pagination, but the absence of an output schema makes that less critical.

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 input schema has one required set_id (uuid) with no schema description coverage. The description does not explicitly explain set_id, but 'one comparison set' loosely conveys that the parameter selects which set to read. It partially compensates for the low schema coverage, but leaves the mapping implicit.

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 uses a specific verb ('Read') and names the exact resource ('one comparison set') plus the key scope ('its membership in fixed order'). This clearly separates it from sibling tools like list_comparison_sets, get_comparison_artifact, and get_comparison_verdict.

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 phrase 'one comparison set' implies the use case of retrieving a single set and its membership, and 'Requires comparisons:read' gives a prerequisite. However, there is no explicit statement of when to prefer this tool over alternatives such as list_comparison_sets or get_comparison_artifact.

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