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

Annotations already provide readOnlyHint, idempotentHint, destructiveHint. The description adds bulk support but also introduces contradictory behavior by describing list and list_banco actions, which belong to separate sibling tools. This inconsistency undermines transparency.

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 overly long, detailing three actions when the tool likely only handles 'get'. The verbosity and duplication with sibling tools reduces conciseness.

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?

No output schema exists, so description must detail return values. For the 'get' action, it only says 'fetch full HTML content (componentes + doses)', which is vague. Bulk support is mentioned but not fully explained. Given the tool's complexity and multiple implied operations, the description is incomplete.

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 0%, so description must explain parameters. It covers many (keyword, categoria, incluir_bloqueados, patient_id, manipulado_id, patient_ids, manipulado_ids) but omits 'limite' and 'account'. Partial coverage, but adds meaningful context for the listed 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 lists three actions (list_banco, list, get) but the tool name and '[Flattened action: get]' indicate it should only perform 'get'. This confuses the tool's primary purpose, making it unclear whether it handles multiple operations or just one.

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 write and delete alternatives but fails to distinguish this tool from the sibling list tools (webdiet_manipulados_list, webdiet_manipulados_list_banco), which it implicitly duplicates. No explicit when-to-use guidance is provided.

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