delete-crm-v4-associations-var-var-labels-var_var

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

With no annotations available, the description carries full responsibility for disclosing behavioral traits. 'Delete' gives zero information about what is deleted, whether it is destructive or irreversible, permissions required, or side effects.

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 with a single word, but this is under-specification rather than effective conciseness. The structure lacks any useful information, making it too sparse to be 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?

For a 3-parameter deletion tool with no annotations, output schema, or meaningful schema descriptions, the description must provide substantial context. 'Delete' is completely inadequate for understanding the tool's purpose, usage, or effects.

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%, each parameter description is merely 'Path parameter X', adding no semantic meaning beyond the parameter name. The description 'Delete' does not clarify how fromObjectType, toObjectType, or associationTypeId relate to the deletion operation.

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 'Delete' merely restates the verb in the tool name without specifying what resource or operation it targets. The tool name suggests deleting CRM v4 association labels, but the description provides no object or action detail, making it 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 the many sibling tools, such as put/post/get labels or batch archive operations. No context, prerequisites, or exclusions are provided.

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