Delete records

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

Annotations already declare destructive and non-read-only behavior. The description adds 'permanently' and the ten-record limit, which is useful, but it does not disclose additional behavioral context such as how missing IDs are handled or whether deletion is reversible in any way. No contradiction with annotations.

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 a single, front-loaded sentence with no filler. Every word adds value: 'Permanently' warns about irreversibility, 'delete' states the action, 'up to ten' conveys the batch limit, and 'records' specifies the target.

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?

Given the presence of annotations, an output schema, and only three straightforward required parameters, the description covers the essential action, permanence, and batch limit. It doesn't explain return values (which are in the output schema) or failure modes, but it is largely complete for this tool's complexity.

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?

With 0% schema description coverage, the description must compensate for explaining parameters, but it only says 'records' without detailing baseId, table, or recordIds. The 'up to ten' qualifier matches the schema's maxItems, adding little beyond the field names themselves.

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 uses the specific verb 'delete' with the resource 'records', and adds important qualifiers 'permanently' and 'up to ten'. This makes the tool's purpose unmistakable and distinguishes it from siblings like create_records, update_records, and list_records.

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 'Permanently delete' clearly signals that this tool is for irreversible batch removal of records, which is distinct from create/update/list operations. However, it does not explicitly name alternatives or state when not to use this tool, so it stops short of a perfect score.

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