Delete item

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

Annotations only flag destructiveHint:true, but description adds critical behavior: dry-run default, immutable audit entry, and ATF regulatory constraint. It also explicitly labels the operation as 'Destructive write,' reinforcing the annotation. This goes well beyond the annotation's minimal signal.

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 sentences with zero filler: front-loaded purpose, then constraints, then execution requirement. Each sentence carries distinct information.

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?

The description covers purpose, regulatory constraints, required parameters, and the critical dry-run/confirm execution flow. Given the tool's destructive nature and 5-parameter schema, it is contextually complete; absence of output schema is not a gap.

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 covers 100% of parameters with clear descriptions, so baseline is 3. The description adds meaningful semantics by tying deleteType and deleteNote to the ATF rule and audit immutability, and by explaining confirm's dry-run behavior—value beyond the schema's property definitions.

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?

Description begins with 'Delete a firearm record'—a specific verb and resource that distinguishes this from sibling delete tools (e.g., delete_acquisition_item). It further narrows scope by noting ATF permits deletion only for Duplicate or Error.

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?

Explicitly states dry-run is default and confirm:true is required to execute, giving clear when-to-use guidance. The ATF restriction (only Duplicate or Error) functions as a when-not-to-use condition, and the required deleteType/deleteNote parameters are highlighted, though no alternative sibling tool is named.

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