delete_dependencies

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

The description explicitly warns '⚠️ Irreversible,' which is a critical behavioral trait for a destructive operation. However, since no annotations are provided, the description carries the full burden and does not mention permissions, atomicity, error handling, or other side effects, leaving the disclosure somewhat minimal.

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 front-loaded with the verb and resource, followed by a concise warning label. Every word contributes to understanding the tool's function and critical caveat, with zero wasted text.

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 operation with one parameter, the description covers the essential aspects: what is deleted, how it is identified (by ids), and that the action is irreversible. While it omits details on return values or edge cases, the low complexity and absence of an output schema make this reasonably complete.

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 documents the 'ids' parameter with 100% coverage, and the description adds meaning by clarifying that these are dependency IDs and that the operation is performed 'by ids.' This reinforces the parameter's purpose beyond the generic 'Array of IDs' schema description.

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 installed dependencies by ids,' clearly specifying the action (delete), the resource (dependencies), and the selection mechanism (by ids). This distinguishes it from sibling tools like delete_crons or delete_envs by identifying the exact target resource.

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, nor any prerequisites, exclusions, or recommended scenarios. It merely states the action without contextual cues, leaving the agent to infer usage from the name alone.

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