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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so safety is clear. The description adds that it supports batched execution via patient_ids, which is useful but does not contradict or substantially extend beyond annotations.

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 concise, front-loaded with the core purpose, and uses bullet-like structure to list actions and bulk support. It does not waste words, though the dual-action mention is slightly confusing.

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 6 parameters and no output schema, the description provides basic context (actions, bulk support) but lacks details such as what the summary includes, timezone handling, account specification, and how the tool differs from the sibling list tool. Adequate but not thorough.

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 mentions 'filter by date range/patient' and 'accepts patient_ids for batched execution', providing meaning for start, end, patient_id, and patient_ids. However, account and timezone parameters are not explained.

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 'Read schedule/agenda in Dietbox' but then confusingly mentions two actions: list and summary, with a note 'Flattened action: summary', implying the tool may only do summary. This ambiguity about whether it supports both modes or just summary reduces clarity.

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 does not provide explicit guidance on when to use this tool versus sibling 'dietbox_agenda_list' or 'dietbox_agenda_write'. Although it mentions 'list' and 'summary', it does not clearly differentiate the use cases or recommend alternatives.

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