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

No annotations provided, so description carries full burden. It successfully conveys the comprehensive nature ('all ETH') and directional flow (managed→main), but omits critical financial operation details like gas costs, irreversibility of transfers, confirmation requirements, or whether this operation is atomic across wallets.

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?

Perfect single-sentence structure with zero waste. Front-loaded with action verb 'Sweep', followed by scope ('all ETH'), optional extension ('and optionally tokens'), source ('managed wallets'), and destination ('main wallet'). Every clause earns its place.

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 single-parameter tool with 100% schema coverage and no output schema, the description adequately explains the core mechanism. However, as a financial mutation tool without safety annotations, it should ideally mention gas implications or irreversibility warnings to be fully complete for safe agent 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 coverage is 100%, establishing baseline 3. The description mentions 'optionally tokens' which aligns with the optional token_address parameter, but adds no semantic detail beyond what the schema already provides (e.g., no format examples, validation rules, or behavior when omitted beyond the schema's own description).

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?

Excellent clarity with specific verb 'Sweep' and clear resource identification ('ETH and optionally tokens from managed wallets back to main wallet'). Clearly distinguishes from sibling 'fund_wallets' (outward distribution) and trading tools by specifying the consolidation direction toward the main wallet.

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 explicit when-to-use or alternative guidance provided. However, the phrase 'back to main wallet' implicitly contrasts this tool with 'fund_wallets' (which likely distributes outward) and indicates this is for consolidation/recovery scenarios. Lacks explicit exclusions or prerequisites.

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. It mentions 'Buy' and parameter descriptions note ETH spending, but fails to disclose critical traits: that this is a destructive/spending operation, transaction failure handling across multiple wallets, or that it executes blockchain writes. Missing safety 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?

Single sentence with zero waste. Front-loaded with action ('Buy'), immediately followed by scope ('all managed wallets'), method ('simultaneously via Uniswap V2'), and network ('on Base'). Every word earns its place.

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 100% schema coverage, the description adequately covers the 'what' and 'where', but lacks important contextual details expected for a multi-wallet financial transaction tool without output schema or annotations: return value format, transaction confirmation details, or side effects (e.g., gas costs deducted from wallets).

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%, establishing a baseline of 3. The description adds platform context ('via Uniswap V2 on Base') which implicitly constrains token_address to Base-compatible contracts and slippage_percent to DEX mechanics, but does not explicitly elaborate on parameter formats beyond the schema definitions.

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 provides a specific verb ('Buy'), resource ('token'), and clear differentiators including 'all managed wallets simultaneously', 'Uniswap V2', and 'on Base'. It clearly distinguishes from siblings like coordinated_sell, create_wallet, and fund_wallets through its explicit action and scope.

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?

While the description implies usage through naming ('Buy' vs coordinated_sell) and mentions the execution context (Uniswap V2 on Base), it lacks explicit guidance on prerequisites (e.g., requiring funded wallets first) or when to choose this over alternatives like fund_wallets or coordinated_sell.

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. It successfully discloses the venue (Uniswap V2) and chain (Base), which are critical behavioral constraints. However, it omits key operational details for a financial mutation tool: transaction irreversibility, gas cost implications, failure handling across multiple wallets, and return value 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, dense sentence of 11 words with zero redundancy. Every element earns its place: the action (Sell), subject (token), scope (all managed wallets), protocol (Uniswap V2), and network (Base) are all front-loaded and essential for tool selection.

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 DeFi coordination tool with no output schema or annotations, the description provides sufficient context for basic selection but lacks operational completeness. It omits return value documentation, error handling behavior for partial failures across wallets, and prerequisites like gas token (ETH) requirements on Base.

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 has 100% description coverage, establishing a baseline of 3. The description mentions 'Sell a token' (aligning with token_address) and implies the 'all managed wallets' scope, but adds no additional syntax guidance, format examples, or semantic constraints beyond what the schema already provides for percent_to_sell or slippage_percent.

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 provides a specific verb ('Sell'), resource ('token'), and precise scope ('from all managed wallets via Uniswap V2 on Base'). It clearly distinguishes from siblings like 'coordinated_buy' (sell vs buy) and 'collect_funds' (DEX selling vs fund collection) by specifying the venue and chain.

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 through the 'Sell' action and 'all managed wallets' scope, distinguishing it from buying or single-wallet operations. However, it lacks explicit guidance on when to use this versus 'collect_funds' for consolidation, or warnings about gas requirements and market timing.

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 and successfully discloses critical security behavior: private keys are stored 'in-memory for session only'. It also clarifies the return value (address).

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 efficient sentences with zero waste. The first states the action, the second provides essential security context about key persistence. Front-loaded and appropriately 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?

No output schema exists, and the description compensates by stating the return value (address) and critical security constraints. Adequate for a single-parameter tool with these security implications.

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% (label is fully described in schema). The description adds no additional parameter context, meeting the baseline for high-coverage schemas.

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 ('Generate') with clear resource ('wallet') and distinguishes from sibling 'import_wallet' by specifying 'new random wallet'.

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 explicit guidance on when to use create_wallet versus the sibling 'import_wallet'. The agent must infer that 'random' implies creating new keys while 'import' is for existing ones.

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?

Without annotations, the description carries the burden of behavioral disclosure. It successfully identifies the source wallet (DEPLOYER_PRIVATE_KEY) and equal distribution logic, but fails to mention transaction costs, irreversibility, or what happens if the main wallet has insufficient funds.

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?

Single sentence with zero waste. Information is front-loaded with the action (Send ETH) followed by critical qualifiers (source, destination, method). Every word earns its place.

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 single-parameter financial transaction tool with no output schema, the description adequately covers the core operation but omits expected return values (transaction hash), error conditions, or gas fee implications that would help an agent handle the response.

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, the parameter total_eth_amount is fully documented in the schema itself. The description reinforces the 'equal' distribution aspect but adds no additional parameter syntax, validation rules, or format details 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 action (Send ETH), source (main wallet/DEPLOYER_PRIVATE_KEY), destination (all managed wallets), and distribution method (equally). It effectively distinguishes from sibling tools like collect_funds (which likely reverses the flow) and create_wallet (which creates rather than funds).

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 prerequisites (managed wallets must exist, DEPLOYER_PRIVATE_KEY must be configured) but does not explicitly state when to use this versus collect_funds or coordinated_buy. No explicit 'when-not' guidance is provided.

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. It explains that the tool performs estimation based on wallet count, but fails to disclose whether this is a read-only query, if it consumes API rate limits, or what currency/format the estimate returns.

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 single-sentence description is efficiently front-loaded with no wasted words. It packs the resource (Base gas), action (get/estimate), and parameter relationship (N operations) into 11 words.

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 two-parameter tool without output schema or annotations, the description adequately covers the core function. However, it misses the opportunity to clarify the return value structure (e.g., gas units vs. cost) or confirm read-only safety that annotations would typically provide.

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 coverage, the baseline is 3. The description adds valuable context by specifying 'Base' (likely the network) and linking the two parameters conceptually ('N wallet operations'), which helps the agent understand how num_wallets affects the estimate.

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 specifies the action ('Get', 'estimate') and scope (Base gas price, cost for N wallet operations). It distinguishes from execution-oriented siblings like coordinated_buy/sell by focusing on estimation. However, it doesn't explicitly clarify whether 'Base' refers to the Base L2 network or a base price, which could cause confusion.

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 lacks explicit guidance on when to use this tool versus its siblings (e.g., 'use this before coordinated_buy to estimate transaction costs'). Without such guidance, the agent must infer that estimation should precede execution.

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 provided, so description carries full burden. Critically discloses that the key is 'stored in-memory for session only'—essential security context. However, misses return value description, error handling, and whether this replaces current session wallet or adds to a list.

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 with zero waste. Front-loaded with action ('Import an existing wallet'), followed by critical security constraint. Every word earns its place.

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?

Adequate for a 2-parameter tool with complete schema coverage, given the security-critical storage disclosure. However, lacks description of return value (address? object?) and error cases (invalid key format?), which would be helpful given no output schema exists.

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 has 100% description coverage (hex format, optional label), establishing baseline 3. Description adds storage semantics for private_key ('in-memory for session only'), but does not expand on validation rules or label uniqueness constraints.

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?

States specific verb (import), resource (wallet), and mechanism (by private key). 'Existing' clearly distinguishes from sibling 'create_wallet' which generates new wallets.

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?

Implies usage via 'existing wallet' (contrasting with create_wallet), but lacks explicit when-to-use guidance or prerequisites. Session-only storage hint suggests temporary use cases, but no explicit comparison to alternatives.

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 adds valuable context about what data is returned (ETH balances and optional token balances), but fails to indicate read-only safety, return data structure, pagination behavior for 'all' wallets, or whether this queries a local cache versus the blockchain.

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 of nine words. Every element earns its place: the action (List), scope (all managed wallets), default return data (ETH balances), and conditional behavior (optional token balances). No redundancy or fluff.

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 lack of output schema and annotations, the description should ideally specify the return structure (e.g., 'returns array of wallet objects'). It partially compensates by describing the content (balances) but omits the container format, making it minimally adequate for this simple, single-parameter tool.

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%, with the token_address parameter already well-documented in the schema as 'Token contract address to check balances for (optional)'. The description reinforces this with 'optional token balances' but adds no additional semantic detail beyond the schema, warranting the baseline score.

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') and clear resource ('managed wallets'), distinguishing it from sibling tools like create_wallet, fund_wallets, and import_wallet which perform mutations or imports. It specifies scope ('all') and key data returned (ETH/token balances), though 'managed' could be slightly more explicit.

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 lacks explicit guidance on when to use this tool versus alternatives (e.g., when to list all wallets versus using import_wallet or create_wallet). While it mentions 'optional token balances,' this describes parameter behavior rather than providing usage context or prerequisites.

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