Read a saved open-item check

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so safety is covered. The description adds real value by disclosing that results include 'complete source evidence' and that large reports return paging instructions, but it says nothing about what happens with an unknown or expired id.

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, front-loaded sentences with no filler; the core read behavior comes first and the paging note follows. Minor deduction because the second sentence is somewhat cryptic out of context.

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?

With no output schema, the description carries the burden of explaining returns, which it only partly does ('complete source evidence', paging). It omits where the id comes from and how this differs from report_list/report_page, leaving gaps for an agent choosing among seven sibling tools.

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% — the single `id` parameter is documented only by a UUID v4 regex pattern with no prose. The description never explains what the id identifies (a saved report id presumably from report_list), so it fails to compensate for the schema 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 verb 'Read' and the object 'a saved comparison' give a rough sense of the operation, but 'saved comparison' is vague relative to the tool's actual title ('saved open-item check'). Nothing distinguishes it from siblings like report_page or report_list, which an agent must infer from name 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?

There is no explicit when-to-use or when-not-to-use guidance. The clause 'Large reports return free paging instructions' faintly implies that paging is handled elsewhere (report_page), but no sibling is named and no selection criteria are given.

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