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

The annotations already establish that this is a read-only, non-destructive, closed-world operation. The description adds useful context by saying it surfaces up to 15 related § addresses and is intended as a pre-draft check, but it does not describe permissions, result ordering, or other operational behavior beyond that.

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 a single, dense sentence that front-loads the core action and includes the key usage timing and result limit. It is mostly efficient, though the trailing 'before a draft is written' is separated from the usage context and the sentence is somewhat convoluted.

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 an output schema available, the description does not need to explain return values in detail, and it adequately covers the tool's purpose, inputs, and pre-draft usage. The main remaining gap is the absence of explicit sibling alternatives, but the description is otherwise complete for this optional-parameter read tool.

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 the input schema already documents all three parameters in detail. The description reinforces the text-versus-address alternative and the project context, but it adds no syntax, format, or constraint information beyond what the schema provides. Baseline 3 is appropriate.

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 and resource: it checks a draft, claim, or note against the project record for conflicts or repetitions. It also states the output shape as up to 15 § addresses sharing words or links, which clearly distinguishes this from siblings like search or grep. It does not explicitly name an alternative sibling, so it falls short of 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 gives clear usage context: use it before a draft is written, and it can be used for a passage or for something at an address. It does not explicitly exclude cases or name alternative tools such as search or read, but the timing and input conditions are clear enough to guide selection.

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