Delete a record

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

The description uses 'DESTRUCTIVE', which aligns with the destructiveHint annotation. It adds the contextual note 'for corrections', but does not disclose additional behavioral traits such as authorization needs or reversibility. Given the annotation already provides the destructive hint, the description adds moderate value.

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 extremely concise: a single sentence plus 'DESTRUCTIVE.' Every word serves a purpose, and it is front-loaded with the key action. It could be slightly more structured, but for a simple tool this is effective.

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 present, the description does not need to explain return values. However, it does not highlight the safety guard on the user parameter (defaulting to primary user). The tool is simple, so the description is largely adequate but misses an opportunity to mention the user parameter's role.

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 fully documents all three parameters. The description does not add parameter-level details beyond stating 'by id', which is already in the schema. Baseline score of 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 clearly states the action ('Delete') and the resource ('record'), with the specific scope 'by id (for corrections)'. This distinguishes it from sibling tools like delete_profile, and the 'for corrections' adds purpose context.

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 phrase 'for corrections' implies when to use the tool, suggesting it is intended for fixing erroneous records. However, it does not explicitly state when not to use it or mention alternatives, leaving some ambiguity.

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