Manage Contacts Batch

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

The annotations already declare destructiveHint=true and readOnlyHint=false, so the description's statement 'Batch create, update, or delete contacts' adds no behavioral information beyond what annotations provide. It does not disclose aspects like partial-failure behavior, permissions, or side effects.

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 two sentences, front-loads the core action, and includes a brief consolidation note with zero filler.

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?

The tool is complex, but the input schema is exceptionally rich and the output schema is present. The description adequately identifies the tool's role as a batch mutation endpoint, though it could ideally include a pointer to the singular manage_contact tool for non-batch operations.

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 description coverage is 100%, with detailed per-parameter descriptions in the input schema. The tool description itself adds no parameter-level meaning, so a baseline of 3 is appropriate.

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 a specific verb phrase 'Batch create, update, or delete contacts' that clearly identifies the resource (contacts) and the batch scope. It also distinguishes from siblings by noting it is a consolidated replacement for three prior batch tools, making its role clear.

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 conveys clear context: this is the batch counterpart for contact mutations, and it explicitly says it replaces three older batch tools. However, it does not provide explicit guidance about when to use this instead of the singular 'manage_contact' sibling, nor does it list exclusions.

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