get_token_info

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

No annotations are present, so the description is the only source of behavioral disclosure. It implies a read-only operation but does not state whether networkId is required, what happens for invalid addresses, or what fields are returned. For a tool that returns 'detailed information', this is a significant gap.

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 only one sentence, but it essentially restates the tool name without providing additional context. It is not front-loaded with useful decision-making information, so it doesn't earn 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?

With no output schema and no behavioral annotations, the description should clarify what 'detailed information' includes (e.g., symbol, decimals, supply) and any caveats. The presence of many sibling tools for specific data makes this omission particularly problematic.

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?

The input schema already fully documents both parameters (address and networkId) with clear descriptions and required flags, so schema coverage is 100%. The description adds no additional parameter semantics beyond implying 'specific token'.

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 says 'Get' + 'specific token', which clearly indicates a single-token lookup. However, 'detailed information' is vague—among many sibling tools for prices, balances, holders, etc., it does not specify which aspects of the token are returned. This lacks the specificity needed to differentiate it from get_token_prices or get_token_balances.

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 is provided on when to use this tool versus the many sibling tools. There is no mention of what type of information is included or excluded, so the agent cannot decide between this and get_token_prices, get_token_balances, or other token-specific tools.

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