contacts_batch_delete

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It does not state that deletion is permanent, whether it is reversible, what happens on partial failure, or any required permissions. For a destructive batch operation, this is a significant transparency gap.

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, focused sentence that starts with the action verb and immediately conveys the core functionality. No wasted words, and the structure is front-loaded with the verb+resource.

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 simplicity of the tool (one array parameter) and the absence of annotations or output schema details, the description should compensate by explaining parameter semantics and safety aspects. It does not mention batching limits, permanent deletion, or error behavior, leaving the tool underspecified for reliable use.

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 input schema has zero description coverage for the single required parameter 'resource_names'. The description does not explain what this parameter represents (e.g., contact IDs, emails, resource paths), the expected format, or how to identify contacts. The schema itself only provides the type (array of strings), so the description adds no value for parameter 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 clearly states the action ('Delete'), the resource ('contacts'), and the scope ('multiple ... at once'), which directly distinguishes it from the single-delete sibling 'contacts_delete' and aligns with the batch naming convention.

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 'at once' implies use when deleting multiple contacts, but it does not explicitly contrast with the single-delete tool, mention limits, or exclude other alternatives. The usage context is implied rather than clearly stated.

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