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

Annotations already establish readOnly, idempotent, and non-destructive behavior. The description adds value beyond those by disclosing the required auth scope and by revealing that the tool returns not just the verdict but also the comparisons and the deciding rule. This is useful behavioral context for an agent.

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 entire description is one tight, front-loaded sentence. Every clause contributes either scope or a prerequisite, with no filler or repetition.

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 simple two-parameter read operation, the description covers what is returned, the required permission, and the narrow scope. Since there is no output schema, mentioning the returned contents is sufficient. A small gap is the lack of explicit parameter mapping, but overall the tool is well specified.

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 coverage is 0%, so the description carries the burden of explaining parameters. It references 'verdict' and 'comparisons', which loosely maps to verdict_id and set_id, but it never explicitly states that set_id identifies the comparison set and verdict_id identifies the verdict. The parameter names are self-explanatory, but the description itself does not fully bridge the gap.

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 a clearly bounded resource ('one recorded verdict') while also specifying what comes with it: the comparisons it was asked over and the rule it was decided under. This distinguishes it from related siblings like get_comparison_set or get_comparison_artifact without needing to name them.

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 when to call the tool: when you need a single recorded verdict plus its comparison context and decision rule. It also states the required permission ('comparisons:read'), but it does not explicitly list exclusions or alternatives, so it stops short of a 5.

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