post-crm-v4-associations-var-var-batch-labels-archive_archive

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

With no annotations, the description carries full responsibility for behavioral disclosure. It says 'Delete' but the tool name includes 'archive,' which may imply soft deletion, yet nothing is disclosed about effects, reversibility, permissions, or response. The requirement to send a body is noted but is more about parameters than 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 short but somewhat redundant—'REQUIRES body parameter with request data' and 'Check the inputSchema for required body structure' convey overlapping info. It is front-loaded with the purpose, but a single merged sentence would be tighter.

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 schema is rich and fully explains inputs, but the description omits context about batch semantics, the difference from single-label deletion, and what happens to associations. There is no output schema to clarify returns. For a complex tool, more context would be desirable, but the minimal description is still viable since it points to the schema.

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 coverage is 100%, so the schema fully documents all parameters. The description adds no additional meaning beyond directing the agent to the schema, so the baseline score of 3 is appropriate.

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 clearly states 'Delete Specific Labels,' identifying the verb (delete) and resource (specific labels). However, it does not mention that this is a batch operation, which could confuse it with the sibling tool delete-crm-v4-associations-var-var-labels-var_var that also deletes a label.

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 only notes that a body parameter is required and tells the agent to check the input schema. It provides no guidance on when to use this tool versus the single-label delete tool or other alternatives, and no exclusions.

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