post-crm-v4-associations-var-var-labels_labels

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

With no annotations, the description must disclose behavioral traits, but it only states a generic requirement for a body parameter. It doesn't mention side effects, required permissions, idempotency, response format, or what the created entity represents. 'Create' implies mutation but no further 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?

The description is under-specified, not concise. 'Create.' is a fragment, and the remaining sentence points to the schema without adding value. There is no meaningful structure or front-loaded information.

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 5 parameters, no output schema, and no annotations, but the description does not explain the operation's purpose, return value, or context. It is completely inadequate for an agent to select and invoke the tool correctly, especially with many similar sibling tools.

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 schema descriptions are tautological ('string parameter') and the tool description adds no extra meaning beyond 'check the inputSchema.' The parameter names (fromObjectType, toObjectType, name, label) provide some semantics, but the description itself contributes nothing.

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.' with no resource or object specified, leaving the agent to infer from the tool name that it creates association labels. It does not distinguish from sibling POST endpoints like post-crm-v4-associations-var-var-batch-create_create or post-crm-v4-objects-objtype-objid-associations-var-var_var. The verb is tautological with the HTTP method.

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. The only additional note, 'REQUIRES body parameter with request data,' addresses request format, not usage context. No exclusions or alternative tool references are provided.

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