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 mentions 'best-effort' and the cost, which are helpful, but it doesn't describe the return format, failure behavior, or what happens if the contract lacks token metadata. 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 two sentences, front-loaded with the core functionality and ending with the cost note. No wasted words; it is efficient and scannable.

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?

The tool has moderate complexity with no output schema, so the description should hint at return values. It does not specify what metadata is returned or how it is structured, and the 'best-effort' caveat is vague. Given the single parameter and clear scope, it's borderline adequate but leaves room for ambiguity.

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 schema defines a single address parameter with a regex pattern, which is self-documenting. The description adds no extra meaning about the parameter's purpose or format beyond what the schema provides. Since there is only one parameter, the schema's pattern is sufficient, and the description doesn't degrade it.

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 clearly states the tool inspects Base contract bytecode, token metadata, and common token interfaces. This is a specific verb-resource combination that distinguishes it from sibling tools like base_contract_code (bytecode only) and token-specific tools like base_erc20_balance.

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 implies usage for contract inspection and token interface checks but provides no explicit when-to-use guidance or mention of alternatives. An agent might not know when to prefer this over base_contract_code or base_eth_call, though the token metadata aspect adds a distinguishing hint.

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