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

With no annotations provided, the description carries full responsibility for behavioral transparency. It does not disclose whether the check returns current prices, deviation from $1, or any other metric, nor does it mention prerequisites, data sources, or reversibility (though likely read-only). This lack of detail leaves an agent uncertain about the tool's exact 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 that efficiently communicates the tool's core purpose and supported symbols. It uses no filler, earning a high score for conciseness, though it could have been more informative without becoming wasteful.

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 is insufficiently complete: it fails to specify what a 'peg check' returns, how results are formatted, or the role of the optional contract_address. For a two-parameter tool, an agent would need more context to invoke and interpret results correctly.

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 covers one of two parameters: symbol lists the supported coins (USDT, USDC, BUSD, FDUSD, DAI), but contract_address is undocumented in both schema and description. The tool description merely repeats the symbol list and does not explain what contract_address does or how it interacts with symbol. With 50% schema coverage, the description should compensate but does not.

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 performs a BNB Chain stablecoin peg check for USDT, USDC, BUSD, FDUSD, DAI, which is a specific function distinct from the sibling tools (contract verification, yields, gas, overview, protocol TVL, token risk, wallet intel). It explicitly identifies the resource (stablecoin pegs) and the action (check), so an agent can select it for stablecoin peg queries.

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 gives no explicit guidance on when to use this tool vs other BNB tools, such as bnb_token_risk or bnb_overview. It implies its use for stablecoin peg checks, but does not mention any exclusions or alternatives, leaving the agent to infer context from the tool 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.