outliner.collection_delete

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

No annotations are provided, so the description carries the full burden. It discloses the need for force on non-empty collections, which is key behavioral context. However, it does not specify what happens to contained objects (e.g., orphaned or deleted) or the permanent nature of the deletion.

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 extremely concise with two clauses, no filler, and all words carry meaning. It is front-loaded with the action.

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?

While the description covers the core operation and a key condition, it lacks details about side effects (e.g., object handling), error conditions, or recovery options. Given the number of sibling tools and the complexity of the domain, more context would be beneficial.

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 description adds meaning beyond the input schema by clarifying the condition for the force parameter. The schema already has titles, but the description provides the when-to-use context for force. The collection parameter is not elaborated beyond its name, but it's a standard string identifier.

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 'Delete a collection', which is a specific verb+resource. It distinguishes from sibling tools like create and rename by focusing on deletion. The additional condition about force adds precision.

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 explains when force is required (when collection contains objects or child collections), which guides usage. However, it does not mention alternatives or when not to use this tool, such as when to use outliner.object_unlink instead.

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