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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered structurally. What the description adds beyond them is the composition of each result (pharmacy, delivery address, fulfillment with carrier/tracking number, and fills), which is genuinely useful given there is no output schema.

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?

Three front-loaded sentences of roughly forty words with no filler: purpose first, result shape second. The trailing 'Photon GraphQL: orders.' fragment is a slightly dangling backend hint rather than a fully earned sentence, which keeps it below a perfect score.

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 no output schema, the description largely compensates by describing the nested result composition, and annotations handle the read-safe profile. Missing only secondary operational detail such as default page size, ordering of results, and when to reach for the singular get_order sibling.

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 100%, so all five parameters are already documented with types, enum values, pagination semantics and the pat_… id format. The description only echoes the state enum and the patient filter, adding no syntax or format detail beyond the schema; the baseline of 3 applies.

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?

States a specific verb and resource ('List pharmacy orders') and enumerates the filter dimensions, so the agent knows exactly what this returns. It never names the sibling get_order for single-order retrieval, so differentiation from the singular sibling is left to inference rather than stated.

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 phrase 'filterable by patient and state' implies when the tool is useful, and the enumerated states give the agent a concrete filter vocabulary. There is no explicit guidance on when to prefer this over get_order, no pagination expectations, and no mention of default ordering or result limits.

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