post-crm-v3-associations-var-var-batch-create_create

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

With no annotations, the description carries the full burden for behavioral disclosure. It implies a write operation but does not mention permissions, idempotency, rate limits, or side effects. The example payload contradicts the schema, showing properties objects rather than from/to/type, which is a misleading behavior trait.

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 short, but the example is long, irrelevant to associations, and incorrectly shaped. Every sentence should add value; the example does not, making the structure poor despite the small size.

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?

This is a mutation tool with no annotations and no output schema. The description fails to explain what an association is, how batch creation works, or what a successful response looks like. The misleading example compounds the incompleteness.

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%, so a baseline of 3 is appropriate. However, the description's example actively misrepresents the expected inputs, harming rather than adding meaning. It adds no clarification for fromObjectType, toObjectType, or the structure of inputs beyond what the schema already provides.

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 phrase 'Create a batch of associations' clearly states the verb and resource. However, the example body uses properties like firstname and email, which are not association inputs (schema expects from, to, type). This could mislead an agent about what the tool actually does.

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 given on when to use this tool versus alternatives such as post-crm-v3-associations-var-var-batch-read_read or the v4 batch-create tool. It only states a requirement (body parameter), not usage context or exclusions.

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