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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds real context beyond that: exactly which facets of the order come back, that the call maps to GET /search/orders/{id}, and that transactions are only included on request — though it says nothing about auth or rate limits.

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 sentences, zero filler: the returned data is front-loaded, the optional embed flag is explained second, and the underlying endpoint is appended as a compact anchor. Nothing repeats the schema verbatim.

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 present, the description carries the burden of describing return values and does so at the field-group level. The internal shape of the embedded transactions or billing details is left implicit, which is a small residual gap for a read tool with annotations covering safety.

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 100%, so the baseline is 3, but the description earns a bump by clarifying that include_transactions embeds the order's payments, specifically charges and refunds — a semantic detail the schema's 'Also return the order's transactions' does not convey.

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 (get) and resource (a single order by id) and enumerates the payload it returns: billing details, form, totals, status. That distinguishes it from givingfuel_list_orders and givingfuel_get_transaction without naming them explicitly, so it stops short of a 5.

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 implies the lookup usage (fetch one order by id) and tells the caller how to opt into embedded payments, but it never states when to prefer this over givingfuel_list_orders or givingfuel_get_transaction, nor any prerequisite. Usage is inferable but not spelled out.

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