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 covered. The description adds useful content about what the response contains (useful given there is no output schema), but omits auth/scope requirements and the 'Photon GraphQL: order.' backend pointer adds little for an agent.

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?

Two short sentences with the operation front-loaded and no padding; the returned-field list is dense but informative. The trailing 'Photon GraphQL: order.' fragment is cryptic and borderline waste, which keeps it from a 5.

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?

For a single-resource getter with one fully documented required parameter and no output schema, the description compensates reasonably by enumerating the returned fields. What remains missing (auth requirements, error behavior for an invalid id) is minor for this complexity level.

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% – the single order_id parameter is fully documented with its 'ord_…' prefix convention. The description only restates 'by id' and adds no format or validation detail beyond the schema, so baseline 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 ('Get one order by id') and enumerates the payload it returns (state, patient, pharmacy, address, fulfillment/tracking, fills). The singular 'one order by id' scope naturally differentiates it from the sibling photonhealth_list_orders without the agent needing to open either schema.

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?

Fetching a single order by id implies its use case, and the 'by id' phrasing contrasts implicitly with the list sibling. However, there is no explicit statement of when to prefer this over photonhealth_list_orders, nor any stated prerequisites (e.g., needing a valid ord_ id from a prior search).

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