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

With no annotations, the description carries the full burden of behavioral disclosure. It mentions the tool examines holder concentration and contract info, but does not reveal whether it is read-only, how it obtains data, any side effects, or output format. This is insufficient for an agent to anticipate behavior.

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 a single, front-loaded sentence with no redundant words. It efficiently communicates the core purpose and key aspects in under 10 words, perfect for quick scanning.

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?

Given there is no output schema and the tool has only one parameter, the description is too sparse. It fails to explain what the risk assessment result looks like, what 'contract info' includes, or how the output can be used, making it incomplete for an agent to confidently rely on this 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?

The schema has one parameter, contract_address, with 0% description coverage. The tool description implicitly clarifies that this is the BEP-20 token's contract address, adding minimal context. However, it does not elaborate on expected format (e.g., checksummed, BNB chain) or constraints beyond the schema's type and required fields.

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 clearly identifies the resource (BEP-20 tokens) and the action (risk assessment), and specifies two key facets (holder concentration, contract info). It distinguishes itself from siblings like bnb_wallet_intel and bnb_stablecoin_check, though it lacks an explicit action verb, phrasing the purpose as a noun phrase.

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 provides no guidance on when to use this tool versus alternatives such as bnb_contract_verify or bnb_defi_yields. There are no stated conditions, exclusions, or recommended scenarios, leaving the agent to infer suitable usage.

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