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 mentions the data categories but does not disclose response format, time ranges, or any limitations. For a read-only overview, the basic behavior is implied but not explicitly stated.

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 concise sentence, front-loaded with the tool's purpose. Every word contributes to explaining the tool's scope. No superfluous detail.

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 simplicity (no params, no output schema, no annotations), the description is mostly complete for basic invocation. It lists the key data categories covered. However, it could benefit from a note on how this overview relates to sibling tools, but that is covered by purpose clarity.

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 tool has zero parameters, so the description is not required to explain parameters. The baseline for 0 params is 4, and the description makes no irrelevant claims about parameters.

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 provides an overview of the BNB Chain ecosystem, listing specific metrics (price, gas, TVL, block stats). It distinguishes itself from sibling tools that focus on specific aspects (e.g., bnb_gas, bnb_protocol_tvl) by being a comprehensive summary. However, the verb is implied ('overview' rather than an explicit 'get' or 'list').

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?

No guidance is provided on when to use this tool versus alternatives. It does not say 'use this for a quick summary' or 'use specific tools for detailed data'. The agent must infer usage from the name and sibling list.

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