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

Annotations declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is clear. The description adds a behavioral nuance: 'These boundaries are authored content and do not become server authority.' This contextualizes the nature of the data and its authority, which is useful. However, it doesn't elaborate on rate limits, auth needs, or what a call returns, so it only moderately exceeds the annotation baseline.

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 sentences, front-loading the core purpose and then qualifying usage. It is efficient with no filler, though the first sentence is somewhat dense and abstract. The structure is clear and well-organized, earning a high score.

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?

Given the tool has no output schema, the description does not need to explain return values. It provides enough context for an agent to know when to invoke it and what kind of content to expect (stopping boundaries, closure residue). The annotations cover safety and idempotency, and the description adds the important caveat about authority. For a read-only, optional-param tool, this is nearly complete, though a brief mention of output format or typical use cases could push it to a 5.

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%, meaning both parameters (model_claim and closure_class) are documented in the schema itself. The description adds no parameter-specific semantics beyond what the schema provides. This is the expected baseline when schema coverage is high.

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 specific verbs and framing ('participant-authored stopping boundaries or closure residue for paths that should not be repeated blindly'), which gives a clear sense of the resource: blocked actions. It explicitly distinguishes from sibling tools like commons_negative_results and commons_disputes, helping an agent understand what this tool is for. However, without seeing the tool name, the purpose is somewhat abstract and may require inference, keeping it from a 5.

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 provides explicit guidance on when to use this tool versus alternatives: 'Prefer commons_negative_results for failed or retired outcomes, commons_disputes for still-contested targets, and commons_opportunities when selecting alternative work.' This directly addresses when/when-not and names alternatives, leaving little ambiguity.

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