get-crm-v4-associations-definitions-configurations-var-var_var

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

No annotations are provided, so the description carries the full burden of disclosing behavior. The description says only 'Read', which gives no insight into what the function returns, whether it has side effects, authorization requirements, or any other behavioral traits. This is a severe lack of transparency for a tool whose name suggests a complex API endpoint.

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 a single word, which is extremely short but not appropriately concise because it omits nearly all necessary information. This is under-specification rather than conciseness. A useful description would include at least the resource and any key details, but this one provides no value.

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 complex name suggesting a specific CRM v4 endpoint, and the absence of an output schema and annotations, the description is completely inadequate. It does not explain what the endpoint does beyond a generic verb, nor does it mention response format, pagination, or any operational context. The agent cannot infer how to correctly invoke this tool based on this description.

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 provides descriptions for both parameters ('Path parameter toObjectType', 'Path parameter fromObjectType'), reaching 100% schema coverage. Since schema coverage is high, the baseline is 3. The description 'Read' adds no additional parameter semantics, but it doesn't contradict or omit information beyond what the schema already offers.

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 'Read', which is a verb but does not specify what is being read. The tool name indicates it's about CRM v4 association definitions configurations, but the description alone is too vague to distinguish from other 'get' tools. It fails to communicate the resource being acted upon.

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 no guidance on when to use this tool versus alternatives. There is no mention of use cases, prerequisites, or situations where another tool would be more appropriate. The single word 'Read' offers zero contextual usage information.

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