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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It lists what the verification covers but does not mention whether the operation is read-only, potential prerequisites (e.g., contract being verified), possible failure modes, or output format. This leaves the agent without crucial behavioral context.

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 that wastes no words. It efficiently conveys the core function and key aspects in a compact structure, making it easy for an agent to parse quickly.

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 the absence of an output schema and annotations, the description should explain what the tool returns or its conditions. It only lists features, leaving the output format, potential edge cases, and any preconditions unspecified. This is a significant gap for a tool that presumably returns verification details.

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 description coverage is 0%, so the description must compensate. It only implies that contract_address is the address of the contract to verify, without specifying format (e.g., 0x prefix), network specifics, or any constraints. This adds minimal meaning beyond the parameter name itself.

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 states the tool's function with a specific verb ('Verify') and resource ('BNB Chain smart contract'), and lists three distinct aspects (source code, ABI, proxy detection). This specificity distinguishes it from sibling tools like bnb_gas or bnb_defi_yields, which address different concerns.

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 the tool is for verifying contracts but provides no explicit guidance on when to use it versus alternatives, no exclusions, and no mention of alternative tools. It is an implied usage rather than a clear directive.

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