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

This is an annotation contradiction. The description states 'Get TRC20 token metadata,' which implies a read-only, non-destructive operation, but annotations declare readOnlyHint=false and destructiveHint=true. The description does not address this contradiction or clarify side effects, leaving the agent with conflicting signals about whether invoking this tool may alter state or destroy data.

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 a single concise sentence that front-loads the primary action ('Get') and resource, with output fields in parentheses. It contains no unnecessary words and conveys maximum relevant information in minimal space.

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 (one parameter, no output schema), and the description lists the returned metadata fields, which is helpful. However, the contradictory annotations (destructiveHint=true) are not resolved by the description, and there is no mention of safety or side effects. Given that the description should compensate for missing output schema and conflicting annotations, it falls short of full completeness.

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 the only parameter 'contract_address' described as 'TRC20 contract address'. The description does not add additional semantic meaning for the parameter beyond what the schema provides. The baseline of 3 applies because the schema fully documents the parameter, and the description's mention of metadata fields does not enhance parameter understanding.

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 'Get TRC20 token metadata (name, symbol, decimals, total supply)' clearly states a specific verb ('Get') and resource ('TRC20 token metadata'), listing the exact fields returned. It distinguishes from sibling tools like get_trc20_balance and get_trc20_allowance by focusing on metadata rather than balances or allowances.

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 provides no guidance on when to use this tool versus alternatives, nor any exclusions. For example, it does not mention that for TRC20 balances one should use get_trc20_balance or for allowances get_trc20_allowance. Usage context is implied only by the tool name and description, not explicitly communicated.

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