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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does not state whether this is a read-only operation, what side effects it might have, or any permissions or rate limits. The phrase 'Cross-chain distribution, bridge risk' gives no behavioral information at all.

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 extremely short, but it is under-specified rather than concise. It is a fragment rather than a meaningful sentence, and it does not earn its place because it provides minimal actionable information beyond the tool name.

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?

The tool has no output schema and no annotations, so the description needs to explain what the tool returns or how it behaves. It does not, leaving the agent with only a vague topic hint. This is incomplete for a data-retrieval tool, though the simple parameter schema provides some structure.

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 single 'symbol' parameter is fully described in the schema ('Stablecoin symbol e.g. USDC, USDT'), so the description adds no additional semantic value. With 100% schema coverage, the baseline score of 3 is appropriate.

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 'Cross-chain distribution, bridge risk' is a noun phrase with no verb, so it's unclear whether the tool retrieves, calculates, or lists data. It provides some topic indication but does not clearly state its function or distinguish it from sibling tools like 'supply_flow' or 'risk_assessment'.

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 guidance on when to use this tool or when to choose an alternative. It only offers a vague topical phrase, so an agent cannot determine if it's appropriate for a given task or how it relates to sibling tools.

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