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

With no annotations, the description carries the full burden, and it does disclose meaningful traits: the data source is free public data, the output is heuristic rather than authoritative, and there is a $0.01 cost. It does not cover auth requirements, rate limits, or the shape of the returned risk flags.

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?

A single dense sentence listing the checks, followed by a short disclaimer and cost clause; the value proposition is front-loaded. No filler text, though the disclaimer and price could be consolidated slightly.

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 one-parameter, no-annotation, no-output-schema tool, the description supplies the checks performed, the data provenance, the cost, and the non-audit caveat. The main missing piece is any indication of the result format (score vs. flag list), which the agent must infer from the enumerated checks.

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?

One parameter with 0% schema description coverage; the schema only supplies a hex-address regex. The description implicitly tells the agent the address must be a BNB Smart Chain contract, which adds a little meaning, but does not explain the address format or constraints beyond what the pattern already enforces.

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?

States a specific verb and resource (heuristic risk flags for a BNB Smart Chain contract) and enumerates exactly which checks are performed: Sourcify verification, proxy/admin, owner type, mint/pause/blacklist/fee selectors, bytecode size. The BSC scoping cleanly distinguishes it from ethereum_contract_risk and base_contract_risk siblings.

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 an audit or financial advice' line establishes a boundary on what the tool should be used for, and the cost note gives a decision factor. However, there is no explicit guidance on when to prefer this over bsc_address_inspect or the other BSC siblings, leaving the routing to inference.

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