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

Annotations already convey read-only, idempotent, non-destructive behavior. Description adds that the tool handles supplements/herbal medicines and bulk operations, but it contradicts the schema by claiming 'get' action while the tool is named 'list' and standalone 'get' tool exists. The 'flattened action: list' note is confusing.

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?

Description is relatively short and front-loaded with purpose. Each part (differentiation, actions, bulk support) is discernible, though the action listing and flattening note introduce redundancy and confusion.

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?

Given 0% schema description coverage and no output schema, the description provides essential context but lacks clarity on exact functionality (list vs. get). It covers bulk operations but omits pagination, search details, and return value expectations.

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 has zero parameter descriptions, so the description must compensate. It explains patient_id/prescription_id for individual and patient_ids/prescription_ids for bulk retrieval. However, it does not explain skip, take, search, or account parameters, leaving significant gaps.

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?

Description states it reads supplement/herbal medicine prescriptions, distinguishing from meal plans. However, it lists multiple actions (list, get, list_models) that overlap with sibling tools, and the 'flattened action: list' notation creates ambiguity about the tool's actual scope.

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 exclusion for meal plans (use dietbox_meal_plan) but does not direct users to sibling tools like dietbox_prescription_get for single prescriptions. The described actions contradict the separate existence of get and list_models tools, offering no guidance on when to use this list tool vs. those.

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