get_token_info_by_ticker

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

The annotation openWorldHint=true already signals a safe, likely read-only operation. The description adds minimal behavioral context beyond that, such as the notion of 'configured token' but no details on error behavior, required chain context, or what happens when the ticker isn't found. With annotations covering the safety profile, this is adequate but not enriching.

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?

Exactly one sentence, front-loaded with the verb and resource, no filler or repetition. Every word earns its place.

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?

The tool is simple, but the description only gives partial return information ('like contract address and decimals') and doesn't explain what 'configured token' means or how the optional chainId affects the lookup. With no output schema, the description should carry more weight, so this is minimum viable.

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% for both parameters (ticker and chainId), so the schema already fully explains each parameter. The description adds no extra parameter context beyond restating that lookup is by ticker, which is already in the schema. 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?

The description clearly states the tool gets token information by ticker symbol, giving examples (contract address, decimals). However, it doesn't differentiate from the closely related sibling get_token_info_by_symbol, so it falls short of a 5.

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?

No guidance on when to use this tool versus alternatives like get_token_info_by_symbol or market_get_ticker. The description implies a 'configured token' context but doesn't explain when that context applies or when to choose this over other token lookup tools.

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