Preview a removal

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, and the description reinforces the no-deletion guarantee. It adds genuinely useful behavior beyond annotations: what happens to non-food ids (they appear in 'missing') and that data.ok flips to false in that case.

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?

Front-loaded with the core purpose and the safety guarantee in the first clause; the rest is dense but each clause carries a distinct fact (return shape, error signal, workflow ordering, output presentation rule). No filler sentences.

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?

With an output schema present the description need not enumerate return fields, yet it still explains the would_remove/missing split and the data.ok=false condition. Nothing an agent needs to invoke this correctly, or to interpret the preview, is missing.

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?

Schema coverage is 100%, and the schema already documents 'date' (including the get_today counting rule) and 'row_ids' (sourced from get_day). The description references row_ids but adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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+resource ('Show what remove_items would delete, without deleting anything') and explicitly contrasts itself with the sibling that performs the real deletion. An agent can distinguish preview_removal from remove_items without opening either schema.

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?

Gives an explicit when-to-use directive ('Call it before remove_items') and a usage rule about output handling ('name the foods to the user, not their row_ids'). It names the alternative tool and the condition that selects this one.

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