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

With no annotations, the description carries the full burden. It does useful work by disclosing that refresh=true triggers a live pull from the provider (implying extra latency or provider round-trip) and by listing the returned profile fields. It says nothing about auth requirements, error behavior, or whether refresh has cost/side effects.

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 tight sentences, no waste, and the return payload is front-loaded before the refresh caveat. Every clause earns its place.

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 read-only, two-parameter lookup with no output schema, the description adequately covers what is returned (profiles and their key fields) and the one behavioral modifier (refresh). It is nearly complete; only permission/error context is absent, which is minor here.

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 schema already documents orderId and refresh. The description's 'refresh=true pulls live usage from the provider' largely restates the schema's 'Refresh usage counters from the provider' with slightly more framing. Baseline 3 is appropriate.

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 (eSIM order) and enumerates what comes back (profiles, activation code, QR, ICCID, usage). It does not explicitly distinguish itself from the generic get_order sibling, so an agent must infer that this one is eSIM-specific.

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 use case (fetch one eSIM order, optionally with live usage) and hints at refresh=true as the variant for fresh data, but it names no alternatives (get_order, list_esim_orders) and states no when-not conditions. Usage is implied rather than prescribed.

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