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

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

With no annotations, the description carries full burden. It only says 'Delete' and requires a body parameter, but doesn't explain that this is a soft-delete/archive (name says archive), whether it's reversible, or what the side effects are. The term 'Delete' may contradict the 'archive' in the tool name.

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 and front-loaded with 'Delete,' but the example is malformed and takes up space while being inaccurate. It's concise but not effectively structured due to the misleading example.

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 batch archive of associations with no output schema, the description is incomplete. It doesn't mention the return format, how it differs from object archive tools, or whether the operation applies to associations between specific object types. The minimal text leaves significant gaps for an AI agent.

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 schema has 100% coverage, but the description's example is misleading: it shows inputs as [{"id": "123"}] while the schema requires each input to have 'from' and 'to' objects. This actively contradicts the schema, providing incorrect guidance for parameter usage.

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 states 'Delete' and 'object IDs to archive,' giving a clear action and an object scope, but it fails to mention this is for associations or that it's a batch archive. This is vague and could be confused with object deletion tools like post-crm-v4-objects-objtype-batch-archive_archive, so it lacks sibling differentiation.

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?

No guidance on when to use this tool versus alternatives. It doesn't state that this is for associations, nor does it mention when batch-archive is preferred over single-delete or read tools. The example is provided but without any context for usage.

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