crm_batch_update_contacts

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

With no annotations, the description carries full burden but only states it's a batch update. It doesn't disclose critical behavioral traits such as permissions required, whether updates are partial or full, error handling for invalid inputs, rate limits, or response format. This is inadequate for a mutation tool with zero annotation coverage.

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, efficient sentence with zero waste. It's appropriately sized and front-loaded, making it easy to parse quickly without unnecessary elaboration.

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 complexity of a batch update tool with no annotations, no output schema, and 0% schema description coverage, the description is incomplete. It lacks details on usage, behavior, parameters, and expected outcomes, making it insufficient for an agent to invoke the tool correctly without guesswork.

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 0%, but the description doesn't add meaningful parameter details beyond implying an array of inputs. It doesn't explain the structure of 'inputs', the required 'id' and 'properties', or the nested property fields. The baseline is 3 due to high schema detail, but the description fails to compensate for the coverage gap.

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 'Update multiple contacts in a single request' clearly states the action (update) and resource (contacts), but it's vague about scope and doesn't distinguish from siblings like crm_batch_update_companies or crm_update_contact. It lacks specificity about what 'update' entails beyond the basic verb.

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 guidance is provided on when to use this tool versus alternatives like crm_batch_update_objects or crm_update_contact. The description implies batch operations but doesn't specify prerequisites, limitations, or comparative contexts with sibling tools.

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