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

Annotations are empty, so the description must carry the behavioral disclosure burden. It adds domain context (bridge types, availability on blockchain accounts) and notes that account_fk cannot be 0. However, it does not explicitly state that this is a read-only operation, nor does it describe side effects, rate limits, or response structure beyond 'a json object'. The information is helpful but incomplete for a fully transparent behavioral profile.

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 contains a duplicated introduction: the first paragraph defines bridge types, then the second paragraph repeats almost the same information ('Returns bridges based on the transfer_type, a bridge is either an on-ramp, an off-ramp or a blockchain. Bridge on-ramps are also called virtual accounts'). This redundancy makes the description unnecessarily long and poorly structured. While the parameter documentation is clear, the overall presentation is not concise.

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 list tool with five parameters and no output schema details, the description is largely complete. It explains bridge types, parameter origins, transfer_type options, and the account_fk constraint. The output schema indicator exists, so not detailing return structure is acceptable. However, redundancy and the lack of explicit alternative tool guidance slightly reduce completeness, so it does not reach a 5.

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 0%, but the description compensates thoroughly. Every parameter (@api_key, @token, @wallet_fk, @account_fk, @transfer_type) is explained with provenance (e.g., token from /access/login), constraints (account_fk is a database int and may not be 0), and allowed values (transfer_type lists off-ramp, blockchain, on-ramp with concrete meanings). This goes well beyond the bare schema and fully addresses parameter semantics.

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 clearly states 'Returns bridges based on the transfer_type' with a specific verb and resource. It also defines each bridge type (on-ramp, off-ramp, blockchain), which distinguishes this listing tool from sibling operations like bridge_delete, bridge_rename, or bridge_on_ramp. The name 'bridge_list' plus the detailed explanation leaves no ambiguity about its function.

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 provides clear context for when to use the tool: it returns bridges filtered by transfer_type. It also supplies important constraints like 'Bridges are only available on blockchain accounts' and explains the meaning of each transfer_type value. However, it does not explicitly mention alternatives or exclusionary guidance compared to other bridge-related tools, so it stops short of a 5.

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