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

With no annotations, the description carries the full behavioral burden, yet it only restates that this is a delete. It does not say whether deletion is permanent/irreversible, whether it errors when the record is missing, whether it requires a management key with write scope, or what happens to related data.

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?

It is a single economical sentence with no filler, which is the right shape for a simple tool, but at this length it is under-specified rather than genuinely concise — the brevity comes at the cost of any actionable detail.

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, irreversible mutation with no annotations, no output schema, and one undocumented parameter, the definition is materially incomplete. An agent cannot tell the blast radius, permission requirements, or failure behavior before invoking it.

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?

The description adds no parameter meaning whatsoever. record_id has no schema description (the 33% gap), and the significance of passing a manage key (pro_) versus a read-only public key is not reinforced for this destructive operation, so the description fails to compensate for the coverage gap.

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 verb and resource (delete a record) with the containing scope (from a collection), so an agent knows exactly what operation this is. It does not, however, differentiate itself from the sibling mutation tools update_record or create_record beyond the obvious verb, leaving routing to inference.

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?

There is no guidance on when to use this tool versus update_record (which might also remove fields) or how it relates to list_records for locating a record_id. No prerequisites or exclusions are mentioned at all.

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