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

Annotations already declare readOnlyHint and openWorldHint, but the description adds real value beyond them: the per-call cost (0.0030 USDC, first free) and an explicit bound on what the result does and does not cover (not a security audit). It does not mention rate limits or failure modes, keeping it short of a 5.

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?

Two tight sentences front-loaded with the core capability, followed by the scope disclaimer and the pricing detail. Every clause carries information, though the pricing could arguably be split into its own clearly-labeled clause.

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?

With no output schema, the description must carry the return-value burden, and it does: bytecode size, proxy detection details, and owner(). Combined with annotations covering safety and the explicit cost and scope caveats, an agent has everything needed to select and call it correctly.

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 coverage is 100% for the single address parameter, so the schema already documents it fully. The description adds the important context that the address is expected on Base, which is marginally useful beyond the schema's generic "Address (0x...)" wording, matching the baseline 3 for high-coverage schemas.

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 names a specific verb and resource ("Technical profile of a contract on Base") and enumerates the exact outputs: bytecode size, proxy detection (EIP-1167/EIP-1967 implementation and admin), and owner(). The explicit "This is NOT a security audit" cleanly separates it from sibling tools like token-due-diligence.

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 "NOT a security audit" disclaimer scopes when this tool is appropriate and implicitly routes audit needs elsewhere, and the price/free-first-call note gives an invocation condition. It stops short of naming an explicit alternative tool, so it is clear context rather than full when/when-not routing.

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