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

The annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds useful context by calling the quote 'indicative' and listing supported origin pools. It does not disclose quote freshness, expiry, or executability, which are important behavioral details for a bridge quote.

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 sentences, front-loaded with the purpose and then the parameter meanings. Every part earns its place, and the origin-pool list, while long, is directly useful. There is no redundant or filler wording.

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 quote tool with no output schema, the description should ideally say more about amount units and what the quote response contains. It covers origin and destination adequately but leaves amount semantics and return expectations implicit. The definition is minimally viable but has clear 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 description coverage is 0%, so the description must compensate. It defines from as the origin pool with an explicit list of values and to as the destination asset with a reference to blackpool_assets. However, amount is left to the schema pattern only; its units, token decimals, and expected format are not explained.

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 states a specific verb and resource: 'Indicative quote for a private bridge.' It also clarifies the roles of from and to, making the tool distinguishable from sibling tools such as blackpool_assets. It stops short of explicitly differentiating itself from all siblings, but the core purpose is clear.

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 usage by explaining from/to, and it points to blackpool_assets for destination assets. However, it does not explicitly state when to use this tool versus alternatives, nor does it mention when not to use it or that it only returns a quote rather than executing a bridge.

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