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

With no annotations, the description carries the burden of behavioral disclosure. It names the operations and the $0.02 USDC fee, but does not state whether the operation is read-only, what response to expect, whether it makes on-chain calls, or any failure/rate-limit behavior.

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, front-loaded sentence. The parenthetical cost is useful and the three capability terms are ordered clearly without wasted words.

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?

Although the tool has only one parameter, there is no output schema and no description of the return shape, input format, or usage context. An agent could guess it needs an address, but not how to format it or what result to expect, leaving important gaps for reliable invocation.

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 the address parameter beyond implying a smart contract address. It does not specify network, chain, address format, or how the address is used. The description fails to compensate for the lack of schema documentation.

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 identifies three specific functions—source code analysis, ABI fetching, and proxy validation—and the smart-contract context clearly distinguishes it from sibling scraping/analytics tools. It lacks an explicit 'verifies...' verb framing, but the gerunds are specific enough to infer the tool's purpose.

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?

No guidance is provided about when to use this tool versus alternatives such as web_scraper, data_feeds, or base_analytics. The description mentions only the cost, not the conditions, prerequisites, or scenarios that should trigger this tool.

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