Manage Contacts Batch

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

Annotations already indicate destructiveHint=true, readOnlyHint=false. Description adds that it handles create/update/delete actions, which aligns, but does not disclose additional traits (e.g., auth requirements, rate limits, or that it uses People API batch endpoints).

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 that front-load the core purpose and succinctly add context about consolidation. No wasted words.

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?

Covers the basic batch operation and consolidation, but does not describe return values, error behavior, or limits (e.g., batch size), despite the tool's complexity and existence of an output schema.

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% with detailed parameter descriptions (e.g., actions enum, fields in contacts/updates). The description adds no extra parameter meaning beyond stating the actions, so baseline 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?

Description clearly states 'Batch create, update, or delete contacts' using specific verbs and resource, and distinguishes it from siblings by noting it is a consolidated replacement for three separate batch tools.

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?

Implies usage for any batch operation on contacts and references the tools it replaces, but does not explicitly state when to use alternative tools like manage_contact for single contact operations or note any prerequisites.

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