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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuine non-obvious context: it is wallet pay-per-use and returns HTTP 402 when the wallet is too low, an operational precondition the agent cannot get from annotations. It stops short of rate limits or result shape, but the payment/error disclosure is meaningful added value.

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?

Four dense, front-loaded sentences with no filler: purpose, topic modes, payment behavior, and sibling routing. The telegraphic style is efficient, though the run-on clause about symbolexchange is slightly awkward.

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 4-parameter research tool with 100% schema coverage and annotations covering the safety profile, the description covers purpose, routing, valid topic modes, and payment/error behavior. No output schema exists, so return values need not be described, and nothing an agent needs to invoke it correctly is missing.

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 all four parameters including the topic enum and the SYMBOL.EXCHANGE format. The description reinforces the symbolexchange format and lists topic values but adds little beyond structured fields; baseline 3 applies.

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?

States a specific verb (Research) and resource (a tradable asset such as a commodity or currency), and explicitly distinguishes itself from sibling ai_company by routing stocks there. An agent can tell which tool to use without opening either 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?

Gives an explicit use condition (commodity/currency assets) and a named alternative with the selecting condition ('For a stock, use ai_company'). It also enumerates the valid topic modes, leaving virtually nothing to inference.

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