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

No annotations are provided, so the description carries the full burden. It does disclose the cost ($0.005) and enumerates the returned data categories, which is valuable behavioral context. It does not state whether it requires a specific API key, rate limits, or failure modes for invalid/non-existent addresses.

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?

One dense sentence that front-loads the core purpose and then lists returned artifacts, ending with the cost. No filler.

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 single-parameter read tool with no output schema, the description is nearly complete: it enumerates return categories and cost. The only missing pieces are explicit usage guidance versus risk/approvals siblings and any authentication or failure-mode notes.

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% and the description does not describe the single 'address' parameter's format. However, the schema itself enforces a 0x-prefixed 40-hex pattern, so the agent can infer format. The description does not add syntax detail, so baseline applies with a slight gap.

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?

Specific verb 'inspect' paired with a precise resource 'BNB Smart Chain address', and it enumerates exactly what is returned (EOA vs contract vs delegated, balance, nonce, proxy impl, ERC-20 metadata). This clearly distinguishes it from sibling chain variants and from bsc_contract_risk / bsc_token_approvals.

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 ('inspect any address') but provides no explicit when-to-use guidance versus siblings like bsc_contract_risk or bsc_token_approvals. Chain-variant siblings are distinguishable by name alone, but the tool specific to risk/approvals has no routing explanation.

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