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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the bar is lower. The description adds genuinely non-redundant behavior: it is 'provider-reported' and 'may lag final chain state,' which tells the agent not to treat the result as authoritative chain truth.

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 short sentences with the core identity first and the caveat second. Nothing is wasted and it is front-loaded.

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 read-only lookup with no output schema, the identity plus freshness caveat is serviceable, but with four undocumented parameters and no return-shape hint, the definition leaves real gaps an agent would need to guess around.

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% for four parameters (bridge, txHash, toChain, fromChain), and the description mentions none of them. With txHash required and three optional scoping fields, the agent gets no guidance on which of bridge/toChain/fromChain are needed to disambiguate a lookup, so the description fails to compensate for the schema gap.

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?

States a specific verb and resource ('bridge transaction status') and the underlying endpoint, which is enough to separate it from memeswap_xquote (quotes vs. status). It does not explicitly name the sibling it partners with, so it falls short of the top mark.

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 implies the usage context (checking a bridge transaction after submission) via the endpoint and freshness caveat, but never states when to call this versus alternatives like memeswap_xquote or when it is not appropriate. Usage is left to inference.

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