set_etherscan_api_key

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

Discloses persistence (process memory only, not across restarts), security (URL rejection for prompt-injection), and idempotent nature beyond annotations.

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?

Well-structured with clear sections, but slightly verbose; however, all content is valuable and no redundancy.

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?

No output schema, but description adequately explains the side-effects (enables tools, persistence, agent behavior). Could mention return value briefly.

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 covers 100% of param, but description adds crucial details: bare key only, example, where to get, and security constraint (no URL).

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?

Clearly states verb 'Set' and resource 'Etherscan V2 API key' with specific purpose for EVM reads. Distinguishes from sibling like set_helius_api_key.

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?

Explicitly describes when to use (demo-mode flow, enabling tools without restart), precedence over env var, and agent behavior (call immediately, never echo key).

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