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

Describes return values and optional optimization hint. No annotations provided, so description carries burden. Discloses statuses and receiving-chain tx, but no mention of auth, rate limits, or error conditions. Acceptable for a read-only status 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?

Two sentences, no wasted words. Front-loaded with purpose, then provides parameter guidance.

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?

Given the presence of an output schema and high schema coverage, the description fully explains the tool's function, status values, and relationship to bridge_quote. No gaps.

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%. Description adds value by explaining that the 'bridge' parameter comes from bridge_quote and speeds up lookup. This goes beyond the schema's bare description of the parameter.

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?

Clearly states it tracks a cross-chain bridge submitted via bridge_quote, returning DONE/PENDING/FAILED plus receiving-chain tx. Uses specific verb 'Track' and resource 'cross-chain bridge'. Distinguishes from sibling bridge_quote.

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?

Explicitly instructs to pass source-chain tx hash and optionally the bridge tool from the quote for faster lookup. Implies usage context after bridge_quote, but lacks explicit when-not-to-use or alternatives.

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