post-crm-v4-associations-var-var-batch-read_read

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

With no annotations, the description is the sole source of behavioral information. It says 'Read' implying a non-destructive operation, but it does not disclose side effects, auth requirements, rate limits, pagination, or response format. The example shows the request shape but adds no additional behavioral context.

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 extremely concise: 'Read' followed by the key requirement and a compact example. Every word earns its place, and the structure front-loads the purpose. No redundancy or fluff.

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 performs a batch read of associations, but the description lacks essential context: no output schema, no return value explanation, no mention of how fromObjectType/toObjectType work, and no error handling or pagination details. The example only illustrates the request body, leaving the response and broader usage incomplete.

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 descriptions are generic ('string parameter', 'Array of items'), but the example in the description adds some meaning by showing inputs with IDs and properties. However, it introduces 'propertiesWithHistory' which is not present in the schema, potentially confusing users. Overall, the added value is modest given the high schema coverage.

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 states 'Read' and specifies that a body with object IDs and properties is required, but it doesn't explicitly name the resource (associations) or distinguish itself from sibling batch operations like batch-create or batch-archive. The tool name carries the specificity, but the description alone is vague about what exactly is being read.

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?

The description provides a requirement ('body parameter with object IDs and properties') but offers no guidance on when to use this tool versus alternatives. It does not mention context, exclusions, or alternatives among the many sibling association tools.

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