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

There are no annotations, so the description carries the behavioral transparency burden. It does add value by disclosing the returned metadata fields and a $0.001 cost, and 'metadata' implies a read-only operation, but it does not mention errors, rate limits, supported networks, or any side effects. For a simple lookup tool this is adequate but not rich.

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 compact phrase with the key output fields and cost front-loaded. It contains no filler or redundant details, making it easy to scan quickly.

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?

Even though an output schema exists, the three parameters have no schema descriptions and the tool has no annotations, so the description needs to provide more context about chain values, contract format, and when to prefer this over sibling token tools. It is too sparse to be fully actionable in an unfamiliar environment.

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 explain any of the three parameters. Contract, chain, and agent_id are left as raw types and defaults, with no guidance on address formats, allowed chain values, or the meaning of agent_id.

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 names the resource (ERC-20 token) and the expected fields (name, symbol, decimals, total supply), so an agent can infer the tool fetches token metadata even without an explicit verb. It is distinct enough from a token estimate or price tool, though it never explicitly contrasts with a sibling.

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 gives no guidance on when to use this tool versus alternatives like ddg_token_estimate, ddg_crypto_price, or ddg_crypto_portfolio. It does not state when not to use it, what prerequisites exist, or how it differs from similar token-related tools.

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