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

Annotations already provide destructiveHint: true, and the description reinforces this with 'Permanently delete' and 'Irreversible.' It adds the bulk execution detail beyond annotations, but lacks disclosure of other behavioral aspects like permissions or error states.

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 with no wasted words. The first sentence front-loads the primary purpose and irreversibility, and the second adds bulk support information efficiently.

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?

For a delete tool with no output schema and three parameters, the description covers the main action and bulk variant but omits explanation of the 'account' parameter and does not describe the expected response on success, leaving some contextual gaps.

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 description coverage is 0%, so the description must compensate. It explains the array parameter 'calculo_ids' for bulk use but does not clarify the single 'calculo_id' or the 'account' parameter, leaving gaps in understanding for all three parameters.

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 'Permanently delete an energy expenditure calculation. Irreversible.' The verb 'delete' and resource 'energy expenditure calculation' are explicit, and the qualifiers distinguish it from sibling tools like webdiet_calculo_energetico_get or webdiet_calculo_energetico_list.

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 mentions 'Bulk support: accepts calculo_ids for batched execution,' which provides guidance for using the bulk variant. However, it does not explicitly state when not to use the tool or compare it to other delete tools, leaving some context implicit.

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