delete_collection_item

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states the basic delete operation without covering side effects (e.g., irreversibility), required permissions, or what happens to related data. This is insufficient for an agent to anticipate consequences.

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 a single sentence that immediately conveys the verb and target. It is minimally verbose with no filler, making it easy to scan. Every word is essential.

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 deletion tool with three required parameters and an output schema (not shown), the description lacks details on parameter roles, return values, error conditions, or operation behavior. It is too sparse to fully guide an agent, especially given the complexity of selecting the right item.

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 0%, and the description adds no explanation for the three parameters (project_id, selector, unique_id). The agent must infer meanings from parameter names alone, which is risky for 'selector' and 'unique_id' in particular. The description fails to compensate for the schema's lack of descriptions.

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 the action ('Delete') and the target ('an item from a custom collection section'). It distinguishes from sibling delete tools (e.g., delete_document, delete_task) by specifying the collection item context. However, it does not elaborate on what a 'custom collection section' is, leaving some ambiguity.

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 is provided on when to use this tool versus alternatives such as other delete tools or update_collection_item. There are no conditions, prerequisites, or exclusions mentioned, making it difficult for an agent to choose correctly without additional context.

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