make_delete_record

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

With no annotations provided, the description carries full burden. It discloses that only specified keys are deleted, that bulk delete is not supported for safety, and implies an array of keys is expected. It lacks mention of permissions, irreversibility, or side effects, but is otherwise transparent.

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 sentences, no wasted words, front-loaded with the action and resource. Each sentence provides essential information: what it does, how to use it, and a safety caveat.

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 delete operation with two parameters and no output schema, the description adequately covers the tool's behavior: how to delete specific records, what not to do, and a safety note. It could be more complete by mentioning return status or confirmation, but is sufficient for an agent to use correctly.

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%, so the schema already describes both parameters. The description adds value by emphasizing that only the specified keys are removed, reinforcing the 'keys' parameter semantics. It does not add new information for 'data_store_id' but overall enhances understanding.

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 specific verb 'delete' and resource 'record(s) from a Make.com data store by key(s)'. It clearly distinguishes from siblings by stating it only deletes specific records, not all, and explicitly says bulk delete is not supported for safety.

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 description explicitly states when to use (delete specific records by keys) and when not to use (deleting all records is not supported). It provides clear guidance on the intended use case versus alternatives.

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