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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), and the description adds real behavioral context beyond them: the journal is ordered newest-first, includes from/to status, actor and ground, plus created/edited timestamps. It also discloses that 'restingOn' lists dependent issues and merely counts ones the caller may not open — a permission-driven partial-visibility behavior worth knowing.

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?

One front-loaded sentence that starts with the resource and then layers the return-shape detail. The em-dash and parenthetical stack makes it harder to scan than it needs to be, but no sentence is filler.

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?

There is no output schema, so the description correctly spends its budget describing the returned object (journal entries, timestamps, restingOn). The remaining gap is behavior with no identifier supplied — all three parameters are optional, so an agent has no idea what a parameterless call does.

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%, so all three parameters are documented in the schema itself. The description restates the same id-or-(project+label) convention without adding format, precedence, or error semantics beyond it — baseline 3 for a fully documented schema.

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 makes clear this returns a single claim plus its status-change journal, and explicitly distinguishes itself from the listing sibling (see list_claims). The retrieval verb is only implicit ("One claim of a project"), and the sentence is dense with parenthetical detail, but an agent can tell what it gets back versus list_claims.

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?

It routes the agent to list_claims for enumeration and spells out the two valid identification modes ('id', or 'project' plus 'label'), plus the access precondition ('Anybody who sees the project'). It stops short of explicit when-not guidance, e.g. what happens if none of the identifier parameters are supplied.

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