Resolve symbol -> coinId

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

Annotations indicate readOnlyHint=true and destructiveHint=false. The description adds significant behavioral context: paper trading with virtual funds (50,000 mUSD), not financial advice, and detailed execution cost mechanics (taker fees, slippage, etc.) that go well beyond the annotations.

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 verbose, containing many details about execution costs (e.g., paper filling, fees, slippage) that are only tangentially relevant to the resolution task. While front-loaded with the primary purpose, it could be more concise.

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?

An output schema exists (not shown) so return value details are not needed. The description covers the essential usage and behavioral constraints thoroughly, though the execution cost details are somewhat extraneous for a lookup tool.

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%, with descriptions for both 'q' and 'agentTrace'. The description does not add new information about parameters beyond what is in the schema, so 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 resolves human-readable symbols/slugs/names to CoinRithm coinIds (UCID) with disambiguating alternatives. This is a specific verb+resource that distinguishes it from sibling tools that require coinId for trading operations.

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?

Explicitly instructs to use this tool first to obtain the coinId needed by wallet/quote/order tools, and warns not to guess UCIDs because symbols are not unique. This provides clear when-to-use and when-not-to-use guidance.

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