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

Annotations already provide readOnlyHint, idempotentHint, and destructiveHint. The description adds useful behavioral details like bulk support (patient_ids, manipulado_ids) and the structure of returned items for list_banco, exceeding what annotations offer.

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 verbose and disorganized, mixing actions with usage notes and an unclear '[Flattened action: list]' statement. It could be more concise and structured.

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?

Despite multiple actions and 9 parameters, the description does not fully explain parameter interactions or return types for all actions (e.g., list and get lack output details). Output schema is absent, so description should cover this but 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 compensate. It explains keyword, categoria, incluir_bloqueados, patient_id, patient_ids, manipulado_id, manipulado_ids but omits limite and account, providing partial but incomplete parameter documentation.

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 states the tool reads 'Prescrição de manipulados' but lists three actions (list_banco, list, get) while the tool name and '[Flattened action: list]' suggest only list. Sibling tools exist for list_banco and get, causing confusion.

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 tells when to use write/delete siblings, but fails to mention the existence of webdiet_manipulados_list_banco and webdiet_manipulados_get, leaving ambiguity about which tool to use for the listed actions.

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