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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuinely non-structured behavior: results are ordered newest first, output is paged ('rows is one page'), and count_30d is a 30-day total rather than a page-scoped count.

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?

Two tight sentences, with scope front-loaded before the return-shape note. The second sentence is telegraphic ('count_30d is the 30-day total; rows is one page') but every clause carries real information.

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?

With no output schema, the description usefully sketches the return shape (rows plus a 30-day count) and paging behavior. It leaves gaps for a 3-parameter tool with 0% schema coverage: limit bounds, cursor semantics, and address-chain interpretation are all unaddressed.

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 description coverage is 0%, so the description must carry all three parameters, and it does not name any of them. 'newest first' and 'rows is one page' gesture at cursor/limit paging but never state that limit defaults to 25, what cursor encodes, or which chain the address is interpreted on.

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 concrete verb+resource: cross-chain bridge transfers where the given address is sender or recipient, on any chain. That scope cleanly separates it from address-scoped siblings like get_address_bridge_to_earn and aggregate tools like get_crosschain_stats, though it never names an alternative explicitly.

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?

Usage is implied by 'the rows the site's Cross Chain tab shows' and the sender-or-recipient framing, so an agent can infer when this fits. There are no explicit when/when-not rules and no named alternative such as orbitpay_crosschain_history or get_bridge_activity for the aggregate case.

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