Delete a record

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the description need not restate that. It adds non-obvious behavioral facts: deletion requires a separate switch and always returns a staged operation first. This goes beyond annotations and meaningfully sets expectations.

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 three concise sentences with the core purpose first, followed by two high-value caveats. Every sentence earns its place; there is no filler or repetition of schema/annotations.

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 tool with two simple parameters and no output schema, the description provides essential behavior: staged operation first, archive exception, and switch requirement. The main gap is parameter semantics, but the operational guidance is strong enough to make the tool safely invocable.

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 0%, and the description does not define the `resource` or `id` parameters. 'Delete a record' hints that resource is the record type and id is its identifier, but this is too vague to clarify valid resource types or how the id is used. The description adds minimal value beyond the parameter names.

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 states a specific action ('Delete') and resource ('a record'), making the tool's purpose clear. It also distinguishes the tool from create/update operations and explicitly references the archive alternative, differentiating it from a sibling behavior.

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?

It explicitly instructs the agent to check productive_describe_resource for an `archive` action before using delete, giving clear when-to-use-vs-alternative guidance. It also notes the requirement for a special switch beyond ordinary writes, which is a practical precondition for invocation.

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