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

Annotations already declare destructiveHint=true, but the description goes well beyond them: it discloses the exact consequence of the mutation (ratings and run results are orphaned — kept in history, removed from the dataset), an invariant (minimum of one item), and a non-trivial response behavior (may return `needs_confirmation`). This is precisely the added context destructive annotations cannot convey.

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?

Three short sentences, front-loaded with the action, then consequences, then constraints/response behavior. Every sentence carries distinct information and no filler is present.

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 4-parameter mutation tool with no output schema, the description covers the destructive effect, the precondition, and the confirmation round-trip. Minor gaps remain (no mention of permissions or what the return payload looks like beyond needs_confirmation), but the schema covers the remaining parameters.

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 coverage is 100%, so the baseline is 3, but the description adds meaning the schema lacks: it explains the trigger for `needs_confirmation` and therefore the existence/purpose of the `approvalId` parameter, which the schema only describes circularly. It does not clarify `workspace` scoping, so it is not a full 5.

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 first sentence states a specific verb+resource ("Drops one item"), which is clear and scoped. However, it largely restates the tool title ("Remove one item from a Caliper dataset") rather than distinguishing itself from siblings like caliper_datasets_delete (whole dataset) or caliper_datasets_update_item; the differentiation is inferred, not stated.

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 operational constraints ("A dataset must keep at least one item") and a confirmation flow, but never says when to reach for this tool versus caliper_datasets_update_item, caliper_datasets_delete, or other siblings. No when-not guidance either.

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