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

No annotations, so the description carries the full burden. It discloses error behavior (4xx for EOA/non-ERC-20, not charged), that name/symbol are self-reported, and includes pricing/payment method. Missing rate limits or caching details, but strong for a read-only tool.

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?

Well-structured and front-loaded: use case, inputs, outputs, errors, example, price. Dense but no wasted sentences; the example and price are useful for invocation.

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?

For a tool with no output schema, the description enumerates output fields and error codes, and specifies pricing. An agent has everything needed to call and interpret it.

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%, so baseline 3. The description restates the same parameter roles (holder adds balance/share, spender adds allowance) and adds 'flags unlimited approvals' which is output behavior rather than parameter semantics. Limited added value beyond schema.

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?

States a specific verb (get) and resource (ERC-20 basics on Base) and scopes it to before quoting/transferring/approving. It implicitly distinguishes from siblings like base_token_risk and base_token_flows by focusing on static metadata rather than risk or flows.

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?

Provides a clear when-to-use ('before quoting, transferring or approving'), but does not name alternatives or when-not-to-use. Clear context but no exclusions.

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