remove_empty

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

With no annotations, the description carries the full burden; it does disclose the key safety property that only *empty* pages and folders are removed, so populated content is untouched. It says nothing about reversibility, whether the sibling undo can recover the change, or whether this mutates the live document versus only the draft beyond the single word 'draft'.

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?

A single front-loaded sentence with the action first and the scope qualifier last; every word earns its place and there is no filler.

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?

The output schema covers return values and there are no parameters to document, so the remaining burden is behavioral. For a destructive cleanup operation with no annotations, the description should state whether the removal is undoable and how it relates to the draft lifecycle; that gap keeps it at minimum viable.

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 takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. Schema coverage is 100% and the empty properties object matches the parameterless 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?

States a specific verb ('Drop') and specific resources ('empty pages and empty folders') scoped 'from the draft', which is far more informative than the bare name remove_empty. It doesn't explicitly contrast with near-neighbours like dissolve_folder or reset_draft, so an agent must infer that only already-empty containers are targeted.

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 on when to reach for this versus dissolve_folder, reset_draft, or undo, and no stated preconditions (e.g. an unapplied draft must exist). The agent is left to infer usage entirely from the tool name and sibling list.

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