post-crm-v4-associations-definitions-configurations-var-v_create

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

With no annotations, the description must carry the full burden of behavioral disclosure. It provides none: no mention of what is created, side effects, idempotency, permissions, or return values. The only 'behavioral' content is a misleading example that implies creating standard CRM objects, not association definitions.

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 single sentence plus example is under-specified. It includes an irrelevant example that does not match the tool's actual inputs, wasting the limited space. There is no structure or front-loaded clarity; the 'Create' verb is redundant.

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 tool's complexity (three required parameters, nested array structure) and the lack of annotations or output schema, the description is completely inadequate. It does not explain how to construct a valid request, what the path parameters mean, or the purpose of the inputs. The provided example is incompatible with the schema, leaving an agent without sufficient information to invoke the tool correctly.

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?

While schema coverage is 100%, the schema descriptions are generic ('integer parameter', 'string parameter'). The description's example uses 'properties' with 'firstname'/'lastname'/'email', but the schema requires 'category', 'typeId', and 'maxToObjectIds' inside 'inputs'. It also refers to a 'body' parameter that does not exist in the schema, actively misleading rather than adding meaning.

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 only says 'Create', which merely echoes the tool name's '_create' suffix. It fails to identify the resource (association definition configuration) or the operation's scope, and does not distinguish it from the sibling '_update' tool. The example about creating contacts with firstname/lastname is unrelated to the actual schema, adding confusion.

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 alternatives like get/update/purge variants. The statement 'REQUIRES body parameter' is not a usage guideline and conflicts with the actual schema requiring path parameters and 'inputs'. No context about prerequisites, typical use cases, or exclusions is provided.

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