put-crm-v4-objects-objtype-objid-associations-var-var_var

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

With no annotations, the description carries the full burden of behavioral disclosure. 'Create' reveals nothing about idempotency, side effects, required permissions, or consequences of overwriting existing associations. The PUT method in the name suggests replacing associations, but the description does not confirm.

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 under-specified, consisting of a single word 'Create'. This is not genuine conciseness but rather a lack of useful information, similar to the 'Process' example that scored 2.

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 a complex tool with 5 required parameters, a nested body array, and no output schema, the description is grossly incomplete. It does not explain the purpose, the relationship between parameters, or any behavioral caveats.

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%, with each parameter having a description, including the body's items with associationCategory and associationTypeId. However, the description adds no semantic meaning beyond the schema, so the baseline of 3 applies.

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 'Create' is a generic verb with no resource or context. It does not state that this tool creates associations between CRM objects, failing to distinguish it from the many sibling post/create 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?

No guidance is provided on when to use this tool versus alternatives. Sibling tools like delete-crm-v4-objects-objtype-objid-associations-var-var_var and get-crm-v4-objects-objtype-objid-associations-var_var clearly perform related operations, but the description gives no usage context.

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