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

Annotations already mark the tool as readOnly and non-destructive, so no safety caveats are needed. The description adds useful context: data source ('transfers pipeline'), 'raw' nature, and the specific aggregation dimensions returned. This is sufficient behavioral transparency for a zero-parameter read-only tool.

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?

A single, tightly worded sentence front-loads the key concept ('Raw cross-chain transfer tallies') and then lists concrete output categories. Every part of the sentence adds value; there is no fluff or repetition of the title.

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?

For a zero-input read-only tool without an output schema, the description fully conveys what an agent will receive: counts by status, source chain, destination chain, and the latest transfer timestamp. No additional input or behavior details are needed for correct invocation.

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 empty input schema already conveys all parameter information. The description correctly implies no input is required by presenting pre-aggregated statistics. Baseline 4 is appropriate because there is nothing for the description to add beyond the schema.

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 uses a specific verb and resource ('Raw cross-chain transfer tallies') and lists exact data dimensions: counts by status, source chain, destination chain, and latest network timestamp. This clearly separates the aggregate stats tool from event-level siblings like get_bridge_activity.

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 phrase 'Raw cross-chain transfer tallies' implies this is for aggregate transfer counts rather than address-level flows or bridge activity, but no explicit when-to-use or alternative tool names are given. An agent must infer when this is preferable to get_bridge_activity or orbitpay_crosschain_history.

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