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

The description adds substantial behavioral context beyond the annotations, including the $0.10 USDC per call cost, x402 payment requirement, supported clients, and documentation URL. It also clarifies the read-only nature by describing outputs rather than side effects, consistent with readOnlyHint and openWorldHint.

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 well-structured, leading with the tool's purpose and then providing concise bullet points for payment, client, and docs. Every sentence adds useful information with no redundancy or filler.

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?

Despite the tool's complexity, the description covers the input (none), the data sources, the output shape, and the commercial/payment requirements. With an output schema present and no parameters, the description fully equips an agent to decide when and how to invoke 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 has zero parameters, so the schema is complete and there is no parameter ambiguity. The description adds no parameter details, but none are needed, so the baseline of 4 is appropriate.

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 states the tool provides AI-powered Korean crypto market analysis by combining multiple indicators, and it explicitly lists the output (BULLISH/BEARISH/NEUTRAL signal, confidence score, summary, raw data). This distinguishes it from sibling tools like get_kimchi_premium or get_fx_rate, which cover individual metrics.

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 establishes a clear use case: holistic Korean crypto market analysis with an AI-generated consensus signal. It implies this tool is for when a broad market read is needed rather than individual indicator data, though it does not explicitly name alternative tools or state exclusions.

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