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

Annotations already declare destructiveHint=true and readOnlyHint=false, and the description goes well beyond them: irreversibility, the post-delete journal state (lines kept plus a deletion record), and the write-permission requirement. That is real consequence disclosure an agent needs before calling a destructive tool.

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?

Front-loaded with the action and the irreversibility warning, then the alternative and the permission note — no filler sentences. The phrasing 'with what it rests on' and 'keeps it said' is more literary than precise and costs a little parsing effort.

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 destructive, no-output-schema tool with fully documented parameters, the description covers the gaps that matter: reversibility, side effects on the journal, the safer sibling for false claims, and who may invoke it. Nothing needed to call it correctly is missing.

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% and each of id, label, and project is documented there, so the schema carries the burden. The description only hints at the label parameter ('confirm its label with them first') and adds nothing about how id, label, and project combine, so the baseline of 3 applies.

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?

States a specific verb and resource — 'Remove a claim from a project's register' — and immediately bounds the scope ('for good'), so an agent can tell it apart from set_claim, set_claim_status, and delete_* siblings on other resources. The only soft spot is the ambiguous clause 'with what it rests on', but the core action is unmistakable.

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?

Gives explicit when-to-use ('only when the person asked for this very one to be deleted'), a confirmation step ('confirm its label with them first'), and a named alternative for the common adjacent intent ('A claim that turned out false is not deleted: set_claim_status refuted or retracted'). It even states the permission gate ('Members of the project who may write only').

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