delete_contacts

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

With no annotations provided, the description carries full burden for behavioral disclosure. It only says 'Delete' and provides no information about irreversibility, required permissions, what happens with invalid IDs, or the response format. This is a significant gap for a destructive operation.

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 extremely concise, with a front-loaded main sentence and a clear Args section. Every word adds value, with no fluff or redundancy.

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?

Despite being a simple tool, the description is minimal. It lacks context about when to use this tool over delete_contact or delete_contacts_by_query, and does not disclose potential side effects or limitations. The lack of behavioral detail makes it incomplete for an agent to fully assess the operation.

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 critical meaning beyond the schema by stating that contact_ids is a comma-separated list. Since schema description coverage is 0%, this clarification is essential and helps the agent format the parameter correctly.

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 'Delete one or more contacts by ID,' using a specific verb and resource. It effectively distinguishes itself from singular delete_contact by saying 'one or more' and from query-based deletion by specifying 'by ID.'

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 implies usage when you have contact IDs to delete, but does not explicitly contrast with sibling tools like delete_contact (singular) or delete_contacts_by_query. This leaves the choice somewhat ambiguous despite the 'one or more' hint.

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