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

With no annotations, the description carries the full burden and does disclose the paywall behavior: it returns a payment requirement until a payment, bundle_token, or free-tier api_key is supplied. However, the cost in the description ($0.02) conflicts with the title ($0.10), and 'payment header' does not perfectly match the schema's `payment` parameter.

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 compact and front-loads the cost and endpoint before the functional details. The parenthetical about minting a free key is useful. The price duplication with the title adds slight noise but does not seriously hurt clarity.

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 tool with no output schema and no annotations, the description covers endpoint, cost, usage context, authentication options, and the main return fields. It does not explain address format, error responses, or the exact success response shape, but the core calling contract is clear enough to invoke 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 coverage is 0%, so the description must compensate. It does by explaining that `address` is the target address and that `payment`, `bundle_token`, and `api_key` are alternative credentials for unlocking the call. It does not define formats, but it gives meaningful roles to all four parameters.

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 the specific resource (Base/EVM wallet), the concrete outputs (ENS name, activity summary, USDC balance), and the use case (counterparty screening). This clearly distinguishes it from sibling tools like get_xlm_sentiment or get_base_gas_oracle.

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?

It explicitly states when to use the tool: 'Useful for counterparty screening before a payment.' It also points to get_free_api_key as the way to obtain a free-tier key. It does not list exclusions, but no sibling tool overlaps with wallet intelligence.

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