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

Beyond the annotations (read-only, idempotent, non-destructive), the description discloses substantive behavior: per-item return fields, the single biggest-risk rule, unknown items reported as unknown rather than safe, a report_url, and flagging of unofficial links using tracked names. These are useful behavioral details an agent would not get from annotations alone.

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 two dense sentences, front-loads the core action and scope, and uses the remainder to enumerate outputs and edge-case handling. Every sentence adds useful information without padding.

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?

Although there is no output schema, the description explains the return shape well enough for an agent to understand the result: per-item risk/safety fields, a top overall risk, unknown handling, a report URL, and unofficial-link flags. Annotations cover the safety profile, so no critical behavioral gap remains.

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?

Schema coverage is 100%, so the schema already defines the `items` array and maxItems. The description adds meaningful semantics by explaining that entries may be names, links, @handles, or slugs covering multiple item types, which is not fully conveyed by the schema example.

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 gives a specific verb-resource pair ("Check a whole setup at once") and scopes it to up to 8 bots, exchanges, wallets, swap services, or AI trading connectors. The phrase "whole setup at once" also distinguishes it from a singular check tool.

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 clearly signals when to use this tool: for evaluating an entire multi-item setup rather than a single item. It does not explicitly name the sibling `check` tool or state exclusions, so it falls short of the highest usage-guidance level.

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