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

Goes well beyond the readOnly/openWorld annotations by disclosing a concrete price ($0.1 USD per call), the payment protocol (x402), the exact in-call mechanism (_meta['x402/payment'] with Base USDC), the fallback behavior without payment (returns payment requirements), and an HTTPS alternative endpoint accepting Base USDC or X Layer USD₮0. This is exactly the non-obvious operational detail an agent needs before invoking.

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?

Deliverables are front-loaded, followed by the pricing and payment mechanics in tight sentences with no filler. Every clause (price, protocol, in-call payment key, no-payment behavior, HTTPS endpoint) carries distinct operational information.

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, the description compensates by naming the four artifact types returned. Combined with the complete payment flow and the empty-argument confirmation, an agent has everything needed to call this correctly.

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?

Zero parameters, so baseline is 4. The description confirms 'No arguments,' which aligns with the empty schema and prevents an agent from guessing at optional inputs.

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?

Names a specific scope ('Korea power-grid equipment axis only') and enumerates exactly what is returned: per-company betas, session deviations with percentile, HS 8504 export ledger, and an analyst brief. The region-plus-sector qualifier cleanly separates it from sibling chain_defense, chain_semis, and japan tools.

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?

'Korea power-grid equipment axis only' signals that other axes are served by the sibling chain_* tools, so an agent can route correctly. It stops short of naming those alternatives or stating when-not-to-use, but the scoping constraint is explicit.

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