delete_record

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

"Delete" communicates that the operation is destructive, but no annotations are provided to establish its safety profile. The description does not disclose whether deletion is permanent or soft, whether related data is affected, what permissions are required, or how missing records are handled.

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 single sentence is front-loaded, direct, and contains no filler. Its brevity leaves behavioral gaps, but those are assessed under the other dimensions rather than being wordiness or structural problems.

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 simple two-parameter operation with fully described inputs and an output schema, the description is sufficient to identify the basic invocation without needing to explain return values. However, the absence of annotations makes the missing deletion semantics and side-effect information meaningful gaps for a destructive tool.

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 structured fields already document both required parameters and establish the baseline score. The description reinforces the role of record_id but adds no further meaning about collection identifiers, ID formats, or how the two parameters relate.

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 verb, resource, and targeting method: deleting a record by ID. It is distinguishable from delete_collection and update_record by its wording, but it does not explicitly differentiate itself from any sibling.

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 "by ID" gives minimal implicit context for when to use it, but there are no prerequisites, exclusions, or alternative-tool recommendations. It does not explain when batch_records or delete_collection would be more appropriate.

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