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

The description discloses several behavioral traits: the grading bands (strong_buy >= +80, etc.), the fact that a mid score like -52 is reported as neutral by design, snapshot-based refresh, informational-only nature, and the $0.01 payment requirement. Since no annotations are provided, the description carries the full burden and does so well, though it could mention rate limits or response format.

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 well-organized, front-loading the core verdict and score, then grading bands, then payment and sibling differentiation. It is longer than ideal but every sentence carries useful information; the payment and 402 retry details are necessary for a paid tool.

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 single-parameter tool with no output schema, the description covers the verdict values, score range, grading logic, universe, payment, and sibling distinction. It doesn't describe the exact JSON response shape, but the verdict/score/breakdown are all mentioned. The main gap is the lack of an output schema, but the description compensates reasonably.

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% and the single parameter `symbol` is described in the schema with examples. The description adds the covered universe (KOSPI/KOSDAQ) and example symbols, which reinforces but doesn't significantly extend the schema. Baseline 3 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's purpose: return a bottom/top verdict for one Korean stock or index, with concrete examples and the covered universe. It distinguishes itself from the sibling `pitch` tool by explicitly noting that this tool answers ANY symbol and returns per-timeframe breakdowns.

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 explicitly contrasts with the free `pitch` tool, stating that `pitch` only shows a live verdict for the showcase symbol while this tool handles any symbol in the covered universe. It also provides payment instructions and retry guidance for the 402 challenge, which is essential usage context.

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