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

With only readOnlyHint=false in annotations, the description carries the burden of explaining side effects. It discloses that items are consumed, describes per-item effects, quantity consumption behavior, and battle/flight restrictions. It doesn't cover failure cases or return behavior, but its transparency is strong relative to the minimal annotation set.

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?

The description is dense but every clause conveys necessary information about item categories, effects, quantity rules, and usage constraints. It front-loads the core action and then systematically details behaviors; while long, it earns its length for a tool with many item types.

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 consumable-item tool with no output schema and minimal annotations, the description covers the essential behavioral context: what happens, quantity semantics, and valid usage contexts. It omits edge cases like insufficient item quantity or cooldowns, but the description is largely complete for correct invocation.

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. The description adds value beyond the schema by clarifying that fuel effects accept multiple items and that buffs/power surges consume exactly one, details not fully present in the schema's parameter descriptions. This pushes it above baseline.

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?

The description clearly identifies the operation as consuming a cargo item and enumerates the consumable categories and their effects. It is specific about the resource, but it does not explicitly distinguish this tool from sibling actions like repair, refuel, or jump that could achieve similar outcomes through different means.

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 provides clear contextual constraints: 'Works in battle and mid-flight, except emergency warp requires a real system' and explains quantity rules for different item types. It does not name alternative tools or explicitly state when not to use this tool in favor of a sibling, so it stops short of a top score.

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