crm_batch_create_associations

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 states this is a creation operation but doesn't mention whether it requires specific permissions, if it's idempotent, what happens on partial failures, rate limits, or response format. For a batch mutation tool with zero annotation coverage, this leaves critical behavioral traits undocumented.

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 maximally concise with a single clear sentence that front-loads the essential action. Every word earns its place with no redundancy or unnecessary elaboration, making it efficient for quick comprehension.

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 batch creation tool with 3 parameters (including complex nested structures), 0% schema description coverage, no annotations, and no output schema, the description is severely inadequate. It doesn't explain what associations are, how they differ from regular objects, what the expected response looks like, or any error conditions - leaving too many gaps for effective tool use.

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%, so the description must compensate but provides no parameter information. It doesn't explain what 'associations' are, what 'fromObjectType' and 'toObjectType' represent, or the structure of 'inputs' array. With 3 parameters (including complex nested objects) completely undocumented, the description fails to add meaningful semantics beyond the bare 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 action ('Create multiple associations') and scope ('in a single request'), which is a specific verb+resource combination. It distinguishes from single-association creation tools like 'crm_create_association' by emphasizing batch capability, though it doesn't explicitly mention sibling differentiation beyond the 'batch' aspect.

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 provides no guidance on when to use this tool versus alternatives like 'crm_create_association' for single associations or other batch tools. There's no mention of prerequisites, performance considerations, or error handling for batch operations, leaving the agent with insufficient context for optimal tool selection.

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