delete-crm-v3-objects-quotes-var_var

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

With no annotations provided, the description carries the full burden of behavioral disclosure. The word 'Archive' hints that this delete operation might be a soft delete rather than a permanent deletion, but it does not explain side effects, reversibility, required permissions, or what happens to associated records. This is insufficient 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?

The description is one word, which is under-specification rather than efficient conciseness. There is no sentence structure, no object mentioned, and no context. The description is so sparse that it does not earn its place as a helpful explanation.

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 one parameter, no output schema, and no annotations, so the description is the sole source of context. 'Archive' is completely inadequate for an agent to understand the operation, expected input, or result. It fails to build on the tool name and leaves the agent guessing.

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 the single parameter quoteId documented as a path parameter. The description adds no additional parameter meaning, but since the schema fully describes the parameter, 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 is the single word 'Archive', which provides a vague verb but no resource or explicit action. It does not clearly state that this tool deletes/archives a quote, and it fails to distinguish itself from other delete tools for different object types. This is barely more informative than a tautology, as 'archive' is an ambiguous synonym that could be interpreted as soft delete or a noun.

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. No mention of prerequisites, typical scenarios, or exclusions. The description provides no context for an agent to decide between this and sibling tools like delete-crm-v3-objects-line_items-var_var or post-crm-v3-objects-quotes-batch-archive_archive.

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