get-crm-v4-objects-objtype-objid-associations-var_var

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

With no annotations, the description bears full responsibility for disclosing behavior. It only says "List" and offers nothing about response format, pagination, error conditions, or the fact that it is a read operation. This is a severe lack of transparency.

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?

A single word is not concise; it is under-specified. There is no informative content to judge structure or front-loading. The entire description is a placeholder that should have been a sentence or two.

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 tool has three required parameters, no output schema, and no annotations. The description does not explain the purpose, parameters, return value, or when to use it. It is completely inadequate for an agent to correctly select and invoke the tool.

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 schema coverage is 100%, the parameter descriptions are merely 'Path parameter objectId', etc., which add no real meaning. The description itself does not explain how objectType, objectId, and toObjectType relate to the association query. The tool name gives some hints, but the description fails to compensate for the empty schema semantics.

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 is just the word "List", which does not state what is being listed. It fails to identify the resource (CRM associations) or differentiate from sibling tools like create or delete association operations. The name is more informative, but the description itself is a tautology.

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 such as put-crm-v4-objects-objtype-objid-associations-var-var_var or delete-crm-v4-objects-objtype-objid-associations-var-var_var. The description provides no context about its role as a read-only retrieval operation.

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