delete-crm-v4-objects-objtype-objid-associations-var-var_var

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

No annotations are provided, and the description 'Delete' does not disclose whether the operation is destructive, permanent, requires special permissions, or has side effects. The description carries full burden but reveals nothing about behavior.

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 concise, but it is under-specified. Conciseness should not sacrifice all substance; this fails to earn its place because it repeats the verb from the name without adding 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?

The tool has 4 required parameters, no output schema, and no annotations, yet the description provides no operational context. It is completely inadequate for an agent to understand when or how to invoke this 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 description coverage is 100%, each parameter description is merely 'Path parameter X', which conveys no semantic meaning. The tool description adds no additional information about what these parameters represent or how they relate to the 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 is simply 'Delete', which is a tautology of the verb already present in the tool name. It does not state what resource is being deleted (e.g., associations between CRM objects) or provide any distinguishing detail from sibling delete tools.

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 delete/association tools. The description provides no context about intended use cases, prerequisites, or alternatives.

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