delete-crm-v3-objects-invoices-var_var

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

No annotations are provided, so the description carries full responsibility for disclosing behavior. It says only 'Archive' and does not mention whether this is a soft delete, whether it is reversible, what happens to the invoice, or any side effects. This is completely inadequate for a mutation tool.

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?

While being extremely concise, the description is under-specified. A single word provides no structured information and fails to earn its place as a useful description.

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 simple delete/archive operation with no annotations and no output schema, the description should at least state that it archives an invoice by ID and indicate the effect. The one-word description is grossly incomplete and does not help an agent understand the tool's behavior or return value.

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 has 100% coverage with one parameter (invoiceId) properly described as a path parameter. The description adds no meaning beyond the schema, but the baseline for high schema coverage is 3, and the parameter is already clearly documented.

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 just 'Archive', a vague verb with no resource or scope. It does not clearly state that it deletes or archives an invoice by ID, and it is ambiguous relative to the tool's name which suggests a DELETE operation. This lacks the specificity needed to understand what the tool does.

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 like the batch archive endpoint or other delete operations. The description provides no context for choosing this tool over siblings.

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