make_delete_record

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

With no annotations, the description adds value by clarifying the exact scope of deletion and the safety limitation. However, it lacks details on error behavior or idempotency.

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?

Two well-structured sentences with front-loaded verb and resource, zero wasted words. Concisely conveys core purpose and constraint.

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?

Covers key behavioral constraints but does not describe return value or error handling, which would be desirable given no output schema.

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 coverage is 100% and the description effectively paraphrases the schema's parameter descriptions without adding new semantic details beyond the key constraint.

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?

Explicitly states 'Delete SPECIFIC record(s) from a Make.com data store by key(s)', using a specific verb and resource. The clarification that deleting all records is not supported distinguishes it from potential bulk operations.

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?

Clearly indicates usage for deleting specific records only and explicitly says deleting all records is not supported, providing a clear usage boundary. However, it does not name alternative tools for bulk deletion.

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