search_official_token_address

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

No annotations are provided, so the description carries full burden. It mentions input and output types ('Expects a TokenDetailsRequestContainer, returns a TokenDetailsResponseContainer'), indicating a read-only lookup, but does not disclose other behavioral traits such as idempotency, rate limits, or error conditions.

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 concise with three sentences, no unnecessary words. The most critical information ('Get the official token address and symbol...') is front-loaded, and each sentence adds value.

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?

Given the presence of an output schema (not shown) and only one parameter, the description is fairly complete. It covers purpose, usage context, and basic input/output types. However, it could be improved by mentioning error scenarios or limitations of the lookup.

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 0%, and the description does not add significant meaning beyond the schema. The only mention is the container type, while the schema already defines the 'query' field as 'token symbol or address'. The description fails to elaborate on how to structure the request or any constraints on the query.

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: 'Get the official token address and symbol for a token symbol or token address.' It uses a specific verb and resource, and distinguishes itself from the sibling tool search_token_details by suggesting to try this one first.

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 provides usage guidance: 'Try to use this first to get address and symbol of coin. If not found, use search_token_details to get details.' This clearly tells the agent when to use this tool versus the alternative.

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