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

Adds 'irreversible' and bulk support beyond annotations (destructiveHint=true). Could mention impact on related data, but adequate for a delete tool.

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?

Two sentences, front-loaded with key action, no fluff. Efficient and clear.

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?

Covers essential deletion behavior and bulk capability. However, lacks error handling, prerequisites, and detailed parameter interaction, especially given 5 parameters and no output schema.

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?

With 0% schema description coverage, the description only briefly mentions anamnesis_ids and patient_ids for batch execution. Does not explain how parameters interact, leaving ambiguity.

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?

Clearly states it removes an anamnese from Dietbox, mentions irreversibility and bulk support. Distinguishes from sibling tools like dietbox_anamnese_get, list, write_create, etc.

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?

Provides clear context for use (irreversible deletion, bulk support). Lacks explicit when-not-to-use or alternatives, but given sibling tools, it's clear this is the delete operation.

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