Manage Contacts Batch

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

Annotations already provide readOnlyHint=false and destructiveHint=true, indicating mutation and potential deletion. The description confirms the actions (create, update, delete) but adds no new behavioral context beyond the annotations. With annotations present, a score of 3 is appropriate as the description adds marginal value.

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 sentence that efficiently communicates the tool's purpose and distinguishes it from predecessors. Every word serves a purpose, with no filler 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?

For a complex tool with 6 parameters, 3 actions, and nested schemas, the description is minimal. It does not explain batch behavior, which parameters to use for each action, or error conditions. However, the presence of a comprehensive input schema and output schema reduces the burden on the description, making a score of 3 adequate but not exceptional.

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 baseline is 3. The description does not add meaning beyond what the schema already provides for parameters. It does not explain the relationship between 'action' and the other parameters (contacts, updates, contact_ids), nor does it specify format or constraints beyond schema.

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 tool performs batch create, update, or delete on contacts, and explicitly distinguishes it from siblings by noting it replaces three separate batch tools (batch_create_contacts, batch_update_contacts, batch_delete_contacts).

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?

No explicit when-to-use or when-not-to-use guidance is provided. While it mentions replacing the three batch tools, it does not explain when to prefer this over the singular manage_contact or search_contacts, nor does it specify prerequisites or context for each action.

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