delete_collection

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

Without annotations, the description carries the burden. It explains the behavior of the delete_objects parameter (deletion vs unlinking) and mentions a confirmation return. However, it omits details on permanence, side effects (e.g., effect on child objects), or error scenarios, leaving gaps for an agent.

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 concise with a clear structure (Args and Returns sections). Each sentence adds value, though the delete_objects explanation is slightly verbose but acceptable.

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?

Given the absence of annotations, the description adequately covers the two parameters and return type. However, it lacks edge-case handling, error details, and specifics about the confirmation dict (though output schema exists, it is not provided). The tool is simple, so a 3 is appropriate.

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 provides clear, additional meaning beyond the schema: 'name: Name of the collection to delete' and 'delete_objects: If True, also delete all objects... If False, objects are unlinked but kept in the scene.' Since schema description coverage is 0%, this fully compensates.

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.' The verb-resource pairing is specific, and the name distinguishes it from sibling delete tools (e.g., delete_object, delete_scene). However, it does not explicitly differentiate when to use this tool over alternatives.

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 other delete-related tools (e.g., delete_object, delete_scene). The description only explains the parameters but does not give context for selection criteria or prerequisites.

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