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

No annotations are provided, so the description carries the full behavioural burden. It does add genuine context by disclosing the $0.005 cost and the full data surface returned, which the structured fields do not provide. It still omits read-only confirmation, error behaviour for invalid or non-existent addresses, and output format, so the disclosure is helpful but incomplete.

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 that leads with the verb and scope before listing the returned data, with no wasted preamble. The parenthetical lists (EIP-1967/1167/zos, USDC/USDT/WETH) make it dense but every clause carries information; the only slight cost is that the run-on sentence is harder to parse at a glance.

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 single-address, read-only inspection tool with no output schema and no annotations, the description does the necessary heavy lifting: it enumerates the return surface and the cost. An agent knows what it will get and what it pays. What is missing is secondary: no return-shape detail, no mention of what happens when the address is not a contract or does not exist.

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 single parameter has 0% schema description coverage, so the description must compensate. It does state that the address is an Avalanche C-Chain address and that 'any' address works, which adds chain-scoping meaning. But it never specifies the required format or hex form; the agent must rely on the schema's regex pattern for that, which is only partial compensation.

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 (inspect) and resource (Avalanche C-Chain address) and enumerates exactly what is returned: address type, AVAX balance, nonce, proxy implementation, ERC-20 metadata, and copycat flags. It is clear what the tool does, but it never distinguishes itself from siblings like avalanche_contract_risk or ethereum_address_inspect; the chain is only signalled by the name and the phrase 'Avalanche C-Chain'.

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 phrase 'Inspect any Avalanche C-Chain address' and the output enumeration imply usage for address reconnaissance before interacting with a contract or token. However, there is no explicit when-to-use/when-not guidance, no mention of when to prefer avalanche_contract_risk, avalanche_token_approvals, or token_deep_scan, and no stated prerequisites.

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