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

With no annotations, the description carries the full burden, and it does disclose one genuinely useful behavioral trait: ERC20 values are normalized by decimals() while ERC721 returns a raw count. However, it says nothing about read-only nature, error behavior for non-ERC20/721 or non-existent tokens, or chain-access semantics.

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?

A single front-loaded sentence with zero wasted words. The entity, chain, and both standard-specific behaviors are packed efficiently with no filler.

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?

No output schema exists and no annotations are present, so the description must stand alone. It covers the return-value semantics well for both standards, but leaves the required 'token' parameter's format undefined, which is a material gap for actually invoking the tool.

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 single nested 'token' parameter is undocumented. The description hints it expects a contract via the word 'contract', but never clarifies whether 'token' is a hex address or symbol, nor its format, so it fails to compensate for the coverage gap.

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 states a specific resource (total supply) scoped to Base mainnet and to ERC20/ERC721 contracts, and even distinguishes the two standards' return semantics. It is clearly separable from balance/allowance siblings by resource, but it never names an alternative tool explicitly.

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?

Usage is only implied: an agent infers it should call this when it needs total supply of a token contract. There is no explicit when-to-use statement, no prerequisites, and no mention of when a sibling like base_erc20-balance or base_call would be the better choice.

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