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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, and the description adds meaningful operational context beyond them. It discloses stateless edge-call behavior, request-size and rate limits, demo/L402 payment access, and invalid-input HTTP 400 behavior.

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 three tight sentences with no wasted language. Purpose, alternative-tool routing, and operational constraints are front-loaded in that order.

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?

Given the rich annotations, full schema coverage, and presence of an output schema, the description provides everything needed to select and invoke the tool. It covers scope, alternative, limits, payment/demo access, and error behavior without needing to explain return values.

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%, so the schema already documents both parameters. The description repeats the node_id input and operating_profile default but adds little semantic detail beyond what the schema and enum already provide, making 3 the appropriate 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 states a specific verb and resource: it calculates Lagrange Network Node hourly GJ fuel burn rates, capacity headroom, and offline vulnerability windows. It also explicitly distinguishes the tool from simulate_eve_capacitor_siege, so an agent can identify its role without opening the 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?

It gives an explicit when-to-use condition: balancing steady-state power allocations on a single Lagrange Network Node. It also names the alternative tool and the condition for choosing it: stress-testing capacitor depletion under hostile fleet bombardment should use simulate_eve_capacitor_siege instead.

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