delete-crm-v3-objects-line_items-var_var

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

With no annotations provided, the description must disclose behavioral traits, but it only says 'Archive'. It doesn't clarify whether this is destructive, reversible, requires specific permissions, or what happens to the line item. The description carries the full burden and fails to add any transparency.

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?

A one-word description is extremely concise but not informative. It under-specifies the tool's purpose and behavior, similar to the 'Process' example. The minimal length is not justified by clarity or utility.

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 description is completely inadequate for a tool with no annotations and no output schema. It doesn't explain the operation's effect, return value, or any side effects. The agent is left to infer everything from the tool name and 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?

The schema already describes the lineItemId parameter with the explanation 'Path parameter lineItemId', which gives 100% schema description coverage. The description adds no additional meaning beyond the schema, so a 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 'Archive' is a vague verb that does not specify the resource (line item) or the object being archived. It doesn't clearly distinguish from sibling delete/archive tools, and it's ambiguous whether it means soft-delete or hard-delete. The tool name already conveys more information than the description.

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 provides no guidance on when to use this tool versus alternatives like batch-archive or other delete operations. No context, prerequisites, or exclusions are mentioned, leaving the agent without any usage framework.

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