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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the tool estimates fees, without detailing whether this is a read-only operation, if it requires authentication, rate limits, error conditions, or what the output might look like. For a tool with no annotations, this is insufficient to inform safe and effective use.

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 a single, efficient sentence that directly states the tool's function without unnecessary words. It's front-loaded with the core purpose, making it easy to parse. However, it could be slightly more informative without sacrificing brevity, such as hinting at output or context.

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 complexity of bridge transactions, no annotations, and no output schema, the description is incomplete. It doesn't explain what the estimation returns (e.g., fee breakdown, currency), potential side effects, or how it differs from 'get_bridge_quote'. For a tool in a set with multiple related siblings, more context is needed to ensure proper usage.

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?

The input schema has 100% description coverage, clearly documenting all parameters (fromChainId, toChainId, amount, tokenAddress) with their types and optionality. The description adds no additional semantic context beyond what the schema provides, such as format examples or usage notes. With high schema coverage, a baseline score of 3 is appropriate as the schema does the heavy lifting.

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 the tool's purpose ('Estimate fees for a bridge transaction'), which is clear but vague. It specifies the action ('Estimate') and resource ('fees for a bridge transaction'), but doesn't differentiate from sibling tools like 'get_bridge_quote' or explain what 'bridge transaction' entails. This leaves ambiguity about scope and distinction.

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 no guidance on when to use this tool versus alternatives. It doesn't mention sibling tools like 'execute_bridge' or 'get_bridge_quote', nor does it specify prerequisites, constraints, or typical use cases. This lack of context makes it hard for an agent to choose appropriately among related tools.

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

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While it reveals this is a simulation that returns transaction data (not executing real transactions), it doesn't address important behavioral aspects: whether this requires authentication, rate limits, what specific data is returned, error conditions, or how the simulation differs from actual execution. For a complex 9-parameter tool with no annotations, this is insufficient.

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 extremely concise - a single sentence with parenthetical clarification. Every word earns its place: 'Execute a bridge transaction' establishes the core action, while '(simulation only - returns transaction data)' provides critical behavioral context. There's zero redundancy or unnecessary elaboration.

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 complex bridge transaction tool with 9 parameters (including nested objects), no annotations, and no output schema, the description is inadequate. It doesn't explain what 'transaction data' is returned, how the simulation works, error handling, or the relationship between this tool and its siblings. The agent would struggle to use this tool effectively without significant trial and error.

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 78% (high), establishing a baseline of 3. The description adds no parameter-specific information beyond what's in the schema. While the schema documents parameters well, the description doesn't provide additional context about parameter relationships, validation rules, or usage patterns that would help an agent understand how to properly construct requests.

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 the tool's purpose: 'Execute a bridge transaction' with the important qualifier '(simulation only - returns transaction data)'. This distinguishes it from actual execution tools and indicates it's for testing/analysis. However, it doesn't explicitly differentiate from sibling tools like 'estimate_bridge_fees' or 'get_bridge_quote' which might also involve simulation aspects.

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 context through 'simulation only', suggesting this should be used for testing rather than real transactions. However, it provides no explicit guidance on when to choose this tool versus alternatives like 'estimate_bridge_fees' or 'get_bridge_quote', nor does it mention prerequisites or when-not-to-use scenarios beyond the simulation aspect.

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

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

With no annotations provided, the description carries full burden for behavioral disclosure. While it indicates this is a quote operation (implying read-only), it doesn't specify whether this requires authentication, has rate limits, returns time-sensitive data, or what format the quote will be in. The description is minimal and lacks important behavioral context for a financial 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?

The description is a single, efficient sentence that communicates the core purpose without unnecessary words. It's appropriately sized for what it does convey, though it could benefit from additional context.

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 complex financial tool with 7 parameters (including nested objects), no annotations, and no output schema, the description is insufficient. It doesn't explain what the quote includes (fees, estimated time, success probability), how long quotes remain valid, or what format the response will take. The description leaves too many questions unanswered for proper agent usage.

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?

With 71% schema description coverage, the baseline is 3. The description mentions 'bridging USDC or other tokens between chains' which provides some context for the fromToken/toToken parameters, but doesn't add meaningful semantics beyond what the schema already documents for the 7 parameters.

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 the action ('Get a quote') and resource ('bridging USDC or other tokens between chains'), providing a specific verb+resource combination. However, it doesn't explicitly differentiate this quote tool from the sibling 'estimate_bridge_fees' tool, which might serve a similar purpose.

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 no guidance on when to use this tool versus alternatives like 'estimate_bridge_fees' or 'execute_bridge'. There's no mention of prerequisites, timing considerations, or when this tool would be preferred over other bridge-related tools in the server.

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

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states what the tool does but lacks critical details: it doesn't specify if this is a read-only operation, what the output format is (e.g., list of chain names/IDs), whether it's cached or real-time, or any rate limits. For a tool with zero annotation coverage, this is a significant gap in transparency.

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 a single, efficient sentence that front-loads the core purpose with zero wasted words. It's appropriately sized for a simple lookup tool and earns its place by clearly stating the action and resource.

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 tool's low complexity (1 optional parameter) but lack of annotations and output schema, the description is incomplete. It doesn't explain what 'supported chains' means in practice (e.g., network names, IDs, or compatibility details) or what the return value looks like, leaving the agent uncertain about how to use the results. For a tool in a bridging context, more operational context would be helpful.

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 100%, so the input schema fully documents the single parameter 'includeTestnets'. The description adds no parameter-specific information beyond implying it's about chains. This meets the baseline of 3 where the schema does the heavy lifting, but the description doesn't enhance parameter understanding (e.g., by explaining why testnets matter for bridging).

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 the verb ('Get') and resource ('all supported chains for USDC bridging'), making the purpose immediately understandable. It distinguishes this tool from siblings like 'get_supported_tokens' by specifying it's about chains rather than tokens. However, it doesn't explicitly differentiate from other chain-related tools (none exist in siblings), so it's not a perfect 5.

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 no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing this before bridging), exclusions, or how it relates to siblings like 'estimate_bridge_fees' or 'get_bridge_quote'. This leaves the agent to infer usage from context alone.

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

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states what the tool does but doesn't describe behavioral traits like whether it's a read-only operation, potential rate limits, authentication needs, or what the return format looks like (e.g., list of token objects with details). For a tool with no annotations, this is a significant gap in transparency.

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 a single, efficient sentence with zero waste. It's front-loaded with the core purpose and includes essential scope details. Every word earns its place, making it highly concise and well-structured for quick understanding.

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 tool's moderate complexity (2 optional parameters, no output schema, no annotations), the description is minimally adequate. It covers the basic purpose but lacks details on usage context, behavioral traits, and output format. Without annotations or output schema, the description should do more to compensate, but it meets the bare minimum for a simple read operation.

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 100%, so the schema already documents both parameters (chainId and includeTestnets) with descriptions. The description adds no additional meaning beyond what's in the schema—it doesn't explain parameter interactions, default behaviors, or examples. Baseline 3 is appropriate when the schema does the heavy lifting.

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 the verb 'Get' and the resource 'supported tokens', specifying scope with 'for a specific chain or all chains'. It distinguishes from siblings like get_supported_chains (which gets chains, not tokens) and get_user_balance (which gets balances, not token lists). However, it doesn't explicitly differentiate from other token-related tools since none exist in the sibling list.

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 no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, use cases, or exclusions. For example, it doesn't clarify if this should be used before bridging operations (like execute_bridge) or how it relates to get_bridge_quote. The lack of context makes it unclear when this tool is appropriate.

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

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

With no annotations provided, the description carries full burden for behavioral disclosure but provides minimal information. It doesn't indicate whether this is a read-only operation, what authentication might be required, potential rate limits, or what happens with invalid transaction hashes. The description states what the tool does but not how it behaves.

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 a single, efficient sentence that states the core purpose without any fluff. It's appropriately sized for a simple status-checking tool and gets straight to the point. Every word earns its place in conveying the essential function.

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 bridge transaction status tool with no annotations and no output schema, the description is insufficient. It doesn't explain what status information will be returned, potential error conditions, or how this integrates with the bridge workflow. Given the complexity of blockchain bridging and the lack of structured output documentation, more context is needed.

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?

With 100% schema description coverage, all three parameters are already documented in the schema. The description doesn't add any additional context about parameter relationships, constraints, or usage patterns beyond what's in the schema. The baseline score of 3 reflects adequate but not enhanced parameter documentation.

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 the verb ('Get') and resource ('status of a bridge transaction'), making the purpose immediately understandable. However, it doesn't distinguish this tool from potential sibling tools like 'get_bridge_quote' or 'estimate_bridge_fees' - it's clear what it does but not how it differs from related status-checking tools.

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 no guidance on when to use this tool versus alternatives. With sibling tools like 'get_bridge_quote', 'estimate_bridge_fees', and 'execute_bridge', there's no indication whether this should be used before, after, or instead of those operations. No prerequisites or context for usage are mentioned.

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

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

No annotations are provided, so the description carries full burden. While 'Get' implies a read operation, the description doesn't disclose important behavioral aspects like whether this requires authentication, rate limits, error conditions, or what format the balance returns in. For a financial tool with zero annotation coverage, this is insufficient.

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 a single, efficient sentence with zero wasted words. It's appropriately sized for a straightforward tool and front-loads the essential 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?

For a financial balance-checking tool with no annotations and no output schema, the description is incomplete. It doesn't explain what the return value looks like (numeric balance, formatted string, etc.), error handling, or authentication requirements. The context signals indicate this is a non-trivial tool requiring more behavioral disclosure.

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 100%, so the schema already documents all three parameters thoroughly. The description adds no additional parameter semantics beyond what's in the schema descriptions. This meets the baseline expectation when schema coverage is complete.

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 the tool's purpose with a specific verb ('Get') and resource ('user token balance'), and specifies the scope ('on a specific chain'). It doesn't explicitly distinguish from sibling tools, but the purpose is unambiguous for this domain.

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 no guidance on when to use this tool versus alternatives. With sibling tools like 'get_supported_tokens' and 'get_transaction_status' available, there's no indication of when this balance-checking tool is appropriate versus other read operations.

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