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

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, but it only says 'Update' and gives an example. The example uses 'id' and 'properties', which are not in the input schema, misleading the agent. It does not disclose side effects, permissions, or reversibility.

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 only two sentences, but 'Update.' is pure filler. The example is included but not structured or formatted clearly, and it is inconsistent with the schema. Some brevity is good, but the content is not helpful.

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?

The tool has no annotations, no output schema, and a complex body structure. The description omits the resource being updated, gives a misleading example, and provides no context about the purpose of the update. This is completely inadequate for an agent to use effectively.

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?

The input schema covers 100% of parameters, so the baseline is 3. However, the description's example contradicts the schema (example uses 'id' and 'properties' while schema requires 'typeId', 'category', 'maxToObjectIds'), adding confusion instead of clarity. It does not explain the path parameters or the meaning of the body fields.

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 says 'Update' but does not specify what is being updated. The tool name suggests association definitions configurations, but the description itself gives no resource context. This is vague and fails to distinguish from the sibling create/purge 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 the sibling create or purge tools. It does not mention alternatives, prerequisites, or typical scenarios. The only hint is 'Update', which implies modifying existing resources but nothing else.

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