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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses pricing ($0.1/call), the x402 payment handshake, the exact fallback behavior without payment (returns payment requirements), and the two transport channels with their accepted tokens. That is precisely the operational context an agent cannot infer from structured fields.

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?

Content is front-loaded: scope and payload first, then the exclusion caveat, then payment mechanics. The payment block is long and slightly repetitive ('Price: $0.1 USD per call. Payment: x402.' followed by two channel descriptions), but each element carries necessary operational weight.

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 carries the full burden of describing returns and does so: units on every number, ISO 8601 timestamps with time zones, per-section sources with links and freshness. Combined with the payment fallback behavior, an agent knows both what it gets and how to get it.

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?

The tool takes zero parameters and the description states 'No arguments,' matching the empty schema. There is nothing further to disambiguate, so it sits at the zero-parameter 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 enumerates the exact payload: sector beta vs KOSPI, session deviations with percentile, sector news events, US federal awards, HS 8901 export ledger, and an analyst brief. 'Korea shipbuilding and defense axis only' scopes it to one axis, which implicitly separates it from chain_power and chain_semis, but it never names those siblings directly.

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 scope statement ('Korea shipbuilding and defense axis only') plus the explicit exclusion ('No US-to-defense transmission coefficient is included') give an agent clear conditions for selection. It stops short of naming the alternative tool to call for the excluded data or for other axes.

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