arbitrumoracle

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

With no annotations, the description carries the full burden of behavioral disclosure. 'Monitoring' implies a read-only operation, but it does not specify what the tool returns, whether it is safe, or if it has side effects. The description adds minimal context beyond the tool's name.

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 concise sentence with no unnecessary words. It is front-loaded with the core function and resource, making it highly efficient.

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 has no parameters and no output schema, the description is minimal but adequate to understand its high-level purpose. However, it lacks details about the nature of the monitoring (e.g., historical vs. real-time, what data is covered) and any behavioral caveats. This leaves a moderate gap for a tool with no other structured context.

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 tool accepts zero parameters, so the schema is empty and there is nothing to explain. The description does not need to add parameter information, and the baseline for 0 params is 4.

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 monitors bridge deposit/withdrawal flows on Arbitrum. This is a specific resource and function that distinguishes it from sibling tools like gas tracker or defi yields.

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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites, exclusions, or scenarios where it would be preferred over sibling 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, the description carries full responsibility for behavioral disclosure. It lists analysis categories but does not explain what operations are performed, whether it is read-only, how the address is processed, or what kind of result is produced. This lack of detail leaves significant ambiguity.

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, concise sentence that front-loads the core action ('risk analysis') and then lists the key areas. It contains no fluff or repetition, making it efficient. It could be slightly more structured with a verb, but overall it is well-sized.

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?

The tool likely performs complex analysis across multiple dimensions, but the description provides no information about output format, return values, or how the listed aspects are evaluated. There is no output schema to compensate, and the description is too terse to fully inform the agent about what the tool will return or what side effects it might have.

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 schema already describes 'address' as 'Contract address', and the description reinforces that the tool analyzes smart contracts, implying the address is the contract under review. Since coverage is 100%, the description adds minimal extra meaning beyond what the schema provides, so a baseline score is appropriate.

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 identifies the tool as performing smart contract risk analysis, listing specific aspects (verification, proxy, compiler, license). It distinguishes itself from sibling tools that focus on other domains like yields, liquidity, or token screening. However, it lacks an explicit verb like 'analyze' or 'check', making it slightly less direct.

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?

There is no guidance on when to use this tool versus alternatives. The description does not mention any exclusions, prerequisites, or alternative tools. Users must infer from the tool name and description that it's for contract-level risk assessment.

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, the description carries the full burden of behavioral disclosure, but it only states the high-level purpose and filtering. It does not mention return format, ordering, pagination, or any limitations/caveats. For a read tool this is a minimal but acceptable description; however, more detail would be expected.

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 short sentences, front-loaded with the primary purpose and followed by filtering options. Every word earns its place with no redundancy.

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?

This is a simple tool with 2 optional parameters and no output schema. The description is adequate for selecting and invoking the tool but lacks details about what results will look like or any edge cases. It is a minimum viable description, not complete.

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%, so the baseline is 3. The description only paraphrases the schema ('Filter by TVL and category'), adding no extra meaning beyond what the parameter descriptions already provide.

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 uses a specific verb ('compare') and a clear resource ('DeFi yields across all Arbitrum protocols'), which distinguishes it from sibling tools like arb_liquidity_scan or arb_protocol_health. It clearly conveys the tool's scope and 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 implies usage when comparing yields and provides filtering options (TVL, category) for customization. It does not explicitly state alternatives or when not to use it, but the context is clear enough.

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 for behavioral disclosure. It indicates the data is 'Current' and cost estimates are 'estimates', which hints at approximation, but it does not mention read-only nature, update frequency, or potential sources of data. For a simple read operation, this is minimally adequate but not rich.

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, concise sentence that clearly states the tool's output without unnecessary words. It is front-loaded and every word serves a purpose.

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 simplicity (no parameters, no nested objects, no output schema), the description provides sufficient context by naming the resource (Arbitrum gas prices) and the specific outputs (USD cost estimates for transfers and swaps). It does not specify live data freshness or exact units, but for a gas tracking tool, this is adequate.

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 tool has zero parameters, so there is nothing to explain. The description correctly does not mention parameters, and the baseline of 4 is appropriate given the schema coverage is 100% and no parameters exist.

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 identifies the tool's purpose: providing current Arbitrum gas prices with USD cost estimates for transfers and swaps. It distinguishes this tool from the sibling tools, which focus on other topics like DeFi yields, token risk, and whale watching, though it lacks an explicit verb like 'fetch' or 'display'.

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 does not mention any exclusions, prerequisites, or specific use cases beyond the general statement of gas prices. Given the sibling tools cover different domains, some differentiation is implied, but the description does not explicitly state it.

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 must convey behavioral traits itself. It only states a high-level analysis function without detailing what the output contains, whether it is read-only, or any limitations or side effects. This is a thin disclosure for a tool with no other behavioral context.

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, well-structured sentence that front-loads the core purpose (DEX liquidity and volume analysis) and the scope (Arbitrum exchanges). It contains no filler words or redundant details.

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 simplicity of the tool (zero params, no output schema, no annotations), the description is minimally viable but leaves gaps. It does not specify what the analysis produces (e.g., a list of exchanges with metrics, aggregated volumes) or how it differs from sibling tools like arb_defi_yields in terms of output. This makes it somewhat incomplete for an agent needing to predict the tool's returns.

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 tool accepts zero parameters, matching the schema with 100% coverage. Since there is no input for the description to augment, the baseline of 4 applies—there is no additional parameter information required.

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 identifies the tool's domain—DEX liquidity and volume analysis on Arbitrum—using a specific resource and scope. It distinguishes itself from siblings like arb_defi_yields or arb_gas_tracker, though the verb 'analysis' is somewhat vague compared to actions like 'list' or 'get'.

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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of use cases, exclusions, or prerequisite conditions, leaving the agent to infer usage solely from the tool name and high-level description.

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, the description carries full burden. It discloses the type of data returned (price, TVL, protocol count, chain status), indicating a read-only aggregate snapshot. However, it doesn't specify data freshness or any limitations, but for a simple overview this is adequate.

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, front-loaded sentence that immediately states the tool's purpose and then lists four concrete outputs. Every word earns its place with no redundancy.

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 its zero-parameter input and no output schema, the description fully explains what the tool provides. For a simple overview endpoint, this is complete and actionable.

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 tool has zero parameters, so the description doesn't need to explain parameter details. The schema is empty, and the description adds contextual value by naming the specific data dimensions covered, which is more than a baseline for no-parameter tools.

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 uses a specific verb ('overview') tied to a clear resource ('Arbitrum ecosystem') and lists concrete data points (ARB price, TVL, protocol count, chain status). This distinguishes it from the more specialized sibling tools like arb_defi_yields or arb_gas_tracker.

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 generic usage as a broad overview, but it doesn't explicitly state when to use this tool versus the many specific siblings. No alternatives or exclusions are mentioned, leaving the agent to infer that this is the 'big picture' tool.

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 must carry the full burden of behavior disclosure. It mentions outputs but fails to describe any behavioral traits such as data sourcing, rate limits, error handling, or whether the operation is read-only.

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, front-loaded sentence that efficiently conveys the core function and supported protocols without unnecessary detail.

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?

The tool is simple (one parameter, no output schema, no annotations), and the description covers purpose and parameter semantics. However, it lacks usage guidance and behavioral transparency, making it minimally complete for an agent to use confidently.

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 schema description covers the protocol parameter with examples, but the description adds a fuller list of supported values ('GMX, Aave, Pendle, Camelot, etc.'), providing meaning beyond the schema's minimal example.

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 performs a 'DeFi protocol health check' with specific outputs (TVL, audit status, risk score) and lists supported protocols, which distinguishes it from sibling tools like arb_defi_yields or arb_token_risk.

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 implied usage through the list of supported protocols but does not explicitly state when to use this tool instead of alternatives, nor does it mention exclusions. It gives context but no direct guidance.

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. The verb 'List' implies a read-only operation, which is a behavioral hint, but the description does not explicitly state safety, data source, pagination, or scope limitations. It is minimal but not misleading.

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, front-loaded sentence that conveys all essential information without any filler. Every word earns its place, and it is immediately clear what the tool does.

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 simple no-parameter list tool, the description sufficiently explains the purpose and return nature (a ranked list). However, it does not clarify whether 'major' implies a cutoff or specific ranking details, and with no output schema, a tiny bit more context could improve completeness. Still, it is adequate.

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 tool has zero parameters, so the baseline is 4. The description does not need to add parameter-level details, and the empty schema already captures the fact that no arguments are required.

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 uses a specific verb ('List') combined with a clear resource ('major DeFi protocols on Arbitrum') and a qualifier ('ranked by TVL'). This precisely distinguishes it from sibling tools like arb_protocol_health or arb_defi_yields, which focus on health or yield data.

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 usage context is implied: if you need a ranking of protocols by TVL, this tool is appropriate. However, there is no explicit statement of when to use it versus alternatives, nor any mention of when not to use it or exclusions. Sibling tools exist but are not referenced.

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, the description carries the full burden of behavioral disclosure. It states the tool performs 'supply and risk analysis' but does not clarify whether it is read-only, what data sources are used, what metrics are included, or what the output format is. This is minimal disclosure.

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, concise sentence that conveys the tool's purpose without any fluff. Every word earns its place, and the structure is clean and immediately scannable.

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 parameterless tool with no annotations and no output schema, the description provides a basic understanding of its purpose but lacks detail on the actual risk metrics, methodology, or return value. It is adequate but leaves significant gaps about what the agent should expect.

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 tool has zero parameters, so the baseline is 4. The description adds context about the subject (stablecoins on Arbitrum) but there is no parameter-level information to provide since none exist. This is appropriate for a parameterless tool.

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 identifies the tool as providing stablecoin supply and risk analysis on Arbitrum, naming specific stablecoins. It distinguishes from siblings by focusing on stablecoins, but lacks a strong action verb like 'get' or 'list', which is why it's not a 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?

No guidance is provided on when to use this tool versus alternatives such as arb_token_risk or arb_protocol_health. There is no mention of intended use cases, prerequisites, or exclusions, leaving the agent to infer 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, the description carries full responsibility for behavioral disclosure. It mentions the checks performed but doesn't state whether the operation is read-only, requires special permissions, or has rate limits. It also doesn't describe the nature of the output (e.g., numeric score, category), leaving the agent uncertain about side effects and return format.

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 concise sentence that front-loads the core purpose and includes the key inputs and checks. Every word adds value with no redundancy or filler.

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?

The tool lacks an output schema, so the description should clarify what the returned risk score looks like (range, interpretation, labels) and any caveats. It also does not mention whether the address must be an existing contract or how to handle invalid addresses. Given the tool's simplicity, the description is still incomplete for an agent to fully anticipate behavior.

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 schema provides full coverage for the single 'address' parameter, describing it as 'Token contract address on Arbitrum'. The description adds context about how the address is used (to check verification, proxy, activity) but does not add significant new meaning beyond what the schema already conveys. Baseline 3 is appropriate given high schema coverage.

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 computes a risk score for an Arbitrum token given its contract address, and lists the checks performed (verification, proxy status, activity). This distinguishes it from many sibling tools focused on bridges, gas, or yields, though it doesn't explicitly differentiate from arb_token_screening, which may overlap in 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 implies usage when a token risk score is needed, but provides no explicit guidance on when to prefer this tool over alternatives like arb_token_screening or arb_stablecoin_risk. It doesn't state exclusions or prerequisites beyond having a contract address.

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 mentions verification, risk flags, and AML check, but does not describe what the output looks like, whether it performs external lookups, whether it is read-only, or any failure modes. This leaves significant behavioral ambiguity.

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, well-structured sentence that front-loads the primary purpose and lists three specific sub-functions. Every word contributes value and there is no wasteful repetition.

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?

This is a simple tool with one parameter, but with no output schema and no annotations, the description must provide more context. It does not explain the nature of the results, how to interpret risk flags, or how this tool differs from closely related siblings, leaving meaningful gaps for an agent selecting or invoking it.

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 schema already fully documents the single parameter 'address' with a clear description, providing 100% coverage. The description adds no additional meaning beyond what the schema provides, so the baseline of 3 is appropriate.

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 performs compliance screening for Arbitrum tokens, with specific sub-functions: verification, risk flags, and basic AML check. It is more specific than simply 'token risk' and implies a distinct compliance angle, though it does not explicitly name sibling tools to differentiate itself.

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 phrase 'compliance screening' provides context that this tool is intended for AML/compliance-related token checks, giving an implied use case. However, it does not explicitly state when to use this tool versus alternatives like arb_token_risk or arb_contract_check, nor does it provide exclusions.

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, the description carries the full burden of behavioral disclosure. It only says 'Monitor' and 'Tracks whale movements' without specifying whether this is real-time or historical, what the output format is, or whether it aggregates data. This leaves significant ambiguity about how the tool 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 two short sentences, concise and front-loaded. Every word serves a purpose, and it avoids redundancy.

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?

With no output schema and no annotations, the description should explain what the tool returns and any operational context (e.g., time ranges, data source). It only covers the basic purpose and leaves important gaps for an agent to invoke the tool correctly and interpret results.

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 schema already provides complete descriptions for both parameters (address and min_value_eth), so the baseline is 3. The description's mention of 'large transactions' and 'whale movements' loosely relates to min_value_eth but does not add meaningful parameter semantics beyond the schema.

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 monitors large transactions for any Arbitrum address and tracks whale movements. This distinguishes it from sibling tools like arb_bridge_flows or arb_gas_tracker, which focus on different aspects of Arbitrum.

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 tool is used to track whale activity for a specific address, but it does not explicitly state when to use it over alternatives or mention exclusions. There is no mention of alternatives or conditions for use.

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