removeEmptyCollections

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'Remove all empty collections' implies a destructive operation but doesn't specify whether this is reversible, what permissions are required, whether it affects child resources, or what happens if no empty collections exist. For a potentially destructive tool with zero annotation coverage, this is insufficient.

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, efficient sentence with zero wasted words. It's front-loaded with the core action and target, making it immediately scannable. Every word earns its place in conveying the tool's purpose.

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 this is a potentially destructive operation with no annotations and no output schema, the description is incomplete. It doesn't explain what 'empty' means (e.g., no bookmarks, no subcollections), what confirmation might be needed, what the return value looks like, or error conditions. For a tool that could delete multiple resources, this level of documentation is inadequate.

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 tool has zero parameters with 100% schema description coverage, so the schema already fully documents the input interface. The description doesn't need to explain parameters, and it correctly avoids mentioning any. The baseline for zero parameters is 4, as there's no parameter information to add beyond what the schema provides.

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 ('Remove') and target resource ('all empty collections'), making the purpose immediately understandable. It doesn't differentiate from sibling tools like 'deleteCollection' or 'emptyTrash', but the verb+resource combination is specific enough to convey the tool's function without being tautological.

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 'deleteCollection' (which might handle non-empty collections) or 'emptyTrash' (which might handle trashed items). There's no mention of prerequisites, consequences, or appropriate contexts for invoking this operation.

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