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

The description adds the behavioral guarantee that the returned comparison matches the stored representation exactly, and states the required permission (comparisons:read), which the annotations do not cover. The annotations already declare readOnly, idempotent, and non-destructive; the description does not contradict them.

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 short sentences, each with a distinct purpose: the first describes the operation, the second gives the required permission. No filler words, and the verb comes first.

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?

The tool has a simple two-UUID schema and annotations that declare safety. The description covers purpose, fidelity, and permission. It does not explain the parameters or the domain of 'comparison artifact', but for an agent familiar with the comparison workflow, this is likely adequate.

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 0%, so the description must explain the parameters, but it does not. There is no mention of what set_id and artifact_id refer to, leaving the agent to infer that they identify a comparison set and an artifact within it. This is a significant gap given the 0% coverage.

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 action ('Read'), a specific resource ('one recorded comparison'), and a specific guarantee ('exactly as it was stored'). This clearly distinguishes it from sibling tools like run_comparison, which computes a comparison, or get_comparison_set, which retrieves a set.

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 description gives clear context for use – reading a stored comparison – and adds a prerequisite ('Requires comparisons:read'). It does not explicitly name alternative tools or say when not to use it, but the context is sufficient for an AI agent to select it when needing an exact stored comparison.

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