post-crm-v4-associations-var-var-batch-create_create

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

With no annotations provided, the description carries the full burden for behavioral disclosure. It merely says 'Create' and shows an example, but fails to mention that this creates associations, any side effects, auth requirements, idempotency, or response format. The example even contradicts the schema, making the behavior more confusing rather than transparent.

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 extremely short, which might seem concise, but the single sentence and example are underspecified and misleading. The example does not align with the schema and therefore wastes space. It lacks a clear structure that front-loads core information.

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 complex nested input schema (from, to, types), no output schema, and no annotations, this description is severely incomplete. It does not explain the association concepts, the structure of inputs, or how fromObjectType/toObjectType relate to the batch operation. The agent cannot reliably invoke this tool based solely on the provided information.

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?

Although the schema has descriptions for all parameters, these are generic ('Path parameter toObjectType', 'string parameter') and the tool description adds no meaningful semantic context. Worse, the example provided uses a 'properties' field that does not exist in the schema, directly misleading the agent about what parameters to pass. The description fails to compensate for the schema's lack of explanatory detail.

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 begins with 'Create.' which is vague and does not specify what resource is being created. The tool name suggests batch-creating associations between CRM objects, but the description refers to 'objects to create' and gives an example with contact properties (firstname, lastname, email) that contradicts the actual input schema for associations (from, to, types). Thus the purpose is unclear and misleading.

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?

There is no guidance on when to use this tool versus the many sibling batch-create tools (e.g., v3 vs v4, objects vs associations). The description only mentions a required body parameter, which is a basic requirement rather than situational usage guidance. It does not state prerequisites, exclusions, or alternatives.

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