refresh_esim_usage

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

Bare minimum with no annotations. Description states 'real-time' and 'from carrier' implying network call, but omits error handling, rate limits, or authentication details. No disclosure of 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 sentences, no redundancy. First sentence communicates purpose, second adds prerequisite. Efficient and well-structured.

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?

Adequate for simple tool with 2 parameters and no output schema, but missing description of return value (what does 'update' provide?) and potential error states. Could be improved with typical output or behavior notes.

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 covers both parameters with descriptions. Tool description adds 'requires valid session token' for token but adds no new meaning for orderId. Baseline 3 maintained as schema coverage is 100%.

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?

Clearly specifies the action: request real-time data usage update for an active eSIM. Distinguishes from siblings like cancel_order or get_esim_catalog by unique verb-object pair.

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?

Mentions prerequisite (valid session token) but provides no guidance on when to use this tool versus alternatives or when not to use it. No explicit exclusions or context.

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