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 but fails to specify critical operational details such as the return value format (e.g., wei vs. ether), authentication requirements implied by 'your,' error handling for uninitialized wallets, or rate limiting constraints.

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 consists of a single, efficient sentence of nine words that immediately states the action and resource. There is no redundant or extraneous information; every word contributes to defining the tool's 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?

Given the tool's low complexity (single parameter) and complete schema documentation, the description adequately covers the basic invocation pattern. However, it lacks necessary contextual details regarding the response format and authentication requirements that would be essential without an output schema or annotations.

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 ('Blockchain to check'), establishing a baseline score. The description adds 'specific' to reference the chain parameter and implies personal context with 'your,' but does not augment the parameter semantics with additional format constraints or usage nuances beyond the schema definition.

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 the specific verb 'Get' and clearly identifies the resource as 'your native token balance' with scope 'on a specific blockchain.' While it effectively distinguishes this from portfolio-wide queries through the 'native token' specification, it does not explicitly differentiate from sibling tools like `menese_portfolio` or mention when to prefer this over alternatives.

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 related tools such as `menese_portfolio` (which likely retrieves multi-asset balances) or `menese_send`. It also omits prerequisites such as whether wallet setup via `menese_setup` is required first.

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 disclosure burden. Adds valuable context about persistence ('Jobs persist and execute on-chain') and infrastructure requirements. However, omits safety-critical behavioral traits: no warning about destructive delete action, automatic fund movement risks (despite schema parameter 'allowFundMovement'), or failure modes for conditional triggers.

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?

Three sentences, optimally structured: [1] Core function, [2] Behavioral characteristics with examples, [3] Prerequisites. Zero redundancy; every sentence conveys unique operational information not available in structured fields.

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 17 parameters with 100% schema coverage, the description appropriately focuses on high-level operational context (persistence, canister requirements) rather than parameter details. Deducted one point for missing output behavior description and lack of safety warnings regarding automatic fund transfers, which are critical for this financial automation 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 has 100% description coverage, establishing baseline 3. Description provides helpful examples ('recurring swaps, conditional trades') that map to jobType enum values, adding illustrative context. However, does not explain parameter relationships (e.g., which fields are required for 'create' vs 'conditional' actions) or complex semantics beyond 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?

Clear specific verb ('Manage') + resource ('on-chain scheduled jobs') + mechanism ('via your MeneseAgent canister'). Explicitly distinguishes from sibling tools by focusing on persistent scheduling ('recurring swaps, conditional trades') versus immediate operations like menese_swap or menese_send.

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?

States critical prerequisite ('Requires an agent canister') and setup requirement (env var), implying this is for automated/recurring workflows. However, lacks explicit guidance on when to choose this over menese_swap for immediate execution, or warnings about fund management implications.

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 successfully communicates the broad scope (19 chains) and the wallet dependency, but omits critical behavioral details such as whether data is real-time or cached, rate limiting, specific error scenarios, or the structure/format of the returned portfolio data.

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 consists of exactly two high-value sentences. The first front-loads the action and comprehensive scope (19 chains, specific tokens), while the second states the critical prerequisite. No filler words or redundant phrases are present.

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 absence of both annotations and an output schema, and considering the complexity of aggregating 19 blockchains, the description is minimally adequate but incomplete. It lacks details about the return value structure (balances, USD values, token metadata) and does not explicitly differentiate from menese_balance, which is important for sibling tool selection.

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 contains zero parameters (empty object). Per evaluation guidelines, this establishes a baseline score of 4. The description appropriately does not invent parameter semantics where none 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 uses a specific verb ('Get') and resource ('full portfolio') and clearly defines scope ('across all 19 supported blockchains' plus specific ICP ecosystem tokens). The comprehensive scope distinguishes it from siblings like menese_balance (likely single-chain/account) and menese_prices (market data vs holdings).

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 a clear prerequisite ('Requires a configured wallet'), indicating when the tool is usable. However, it lacks explicit guidance on when to use this versus menese_balance or other siblings, and does not mention error conditions (e.g., what happens if no wallet is configured).

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, description carries full burden. It discloses currency (USD) and freshness ('current'), but omits data source, caching behavior, rate limits, or error handling for unsupported tokens. Baseline adequacy for a read-only lookup 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?

Two sentences with zero waste: first states purpose, second enumerates supported tokens. Information is front-loaded and appropriately sized for the tool's complexity.

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 single parameter with complete schema coverage and no output schema, description adequately covers the tool's scope. Minor gap: lacks return value description or error behavior, but this is acceptable for a simple lookup tool of this type.

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?

While schema has 100% description coverage (baseline 3), the description adds significant value by enumerating 18+ supported token symbols (BTC, ETH, etc.) that the schema lacks as enums. This helps the agent construct valid requests beyond the generic schema 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?

Description uses specific verb 'Get' with clear resource 'current USD prices for crypto tokens'. The token list clearly distinguishes this from trading siblings (menese_swap, menese_send) and account siblings (menese_balance, menese_portfolio).

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?

Purpose is clear enough to imply usage (use when you need price data), but lacks explicit 'when to use' guidance or comparison to siblings like menese_quote which might provide different price contexts. No alternatives or exclusions stated.

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 but discloses almost no behavioral traits. It does not indicate whether operations are read-only, what data format is returned, rate limits, or whether 'quote' actions have side effects like cache updates or transaction preparation.

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 efficiently front-loads the multi-action nature. The colon-separated list structure clearly delineates the three modes. Minor redundancy with 'Multi-action tool' prefix (implied by the action parameter), but otherwise zero waste.

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 complexity (three distinct operational modes, 19 chain options, no output schema, no annotations), the description is minimally viable but incomplete. It omits return value descriptions, authentication requirements, and critical behavioral context needed for a financial/crypto tool handling balances and quotes.

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?

While schema coverage is 100% (baseline 3), the description adds valuable semantic grouping: it maps 'quote' action to swap functionality (linking to fromToken/toToken/amount), 'balance' to chain-specific queries, and clarifies that 'addresses' refers to derived addresses. This contextualizes the action enum beyond the schema's generic 'What to fetch'.

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 enumerates the three distinct operations (get swap quotes, show derived addresses, check single chain balance) with specific verbs and resources. It implicitly distinguishes from sibling 'menese_swap' (quotes vs execution) and 'menese_balance' (single chain vs potentially multi-chain), though 'menese_addresses' functionality appears unique to this tool.

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 this multi-action tool versus specialized siblings (menese_balance, menese_swap). The agent cannot determine if this is a convenience fallback or if specific actions here offer different capabilities than the dedicated 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?

No annotations provided, yet the description fails to disclose critical behavioral traits of this high-stakes financial operation: irreversibility, gas/transaction fees, confirmation times, or authentication requirements. Simply stating 'Send' does not adequately warn of destructive side effects.

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 well-structured sentences with zero waste: first establishes the action, second enumerates supported chains. Efficiently front-loaded with the most critical 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 transaction tool with 5 parameters and no output schema or annotations, the description is dangerously incomplete. It omits fee structures, error handling, return values, and prerequisites (e.g., wallet setup) that are essential for safe invocation.

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, establishing baseline 3. The description enumerates the 19 supported chains, which mirrors the enum in the schema without adding semantic depth to parameter usage (e.g., address formats, amount precision rules).

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 (send) and resource (tokens) with explicit chain enumeration, but inaccurately limits scope to 'native tokens' when the schema supports ERC-20/ICRC-1 via the optional 'token' parameter, potentially misleading users about the tool's full capability.

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?

Provides no guidance on when to use this tool versus siblings like 'menese_swap' or 'menese_quote', and fails to explain when to use 'quote' mode versus 'execute' mode despite the schema offering both options.

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 it explains the three actions, it fails to disclose critical wallet-specific behaviors: whether 'new' overwrites existing wallets, where wallets are persisted, security implications of handling hex seeds, or what return values to expect.

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: first states overall purpose, second efficiently maps the three action values to their specific behaviors. Information is front-loaded and 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?

Given the 100% schema coverage and absence of output schema, the description adequately covers input parameters. However, for a wallet setup tool with no annotations, it lacks completeness regarding side effects (file system persistence), output expectations, and safety warnings about cryptographic material handling.

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 value by explaining the semantic meaning of each enum value for the 'action' parameter (e.g., 'new' generates a fresh wallet), which helps the agent understand the operational impact of each choice beyond the schema's generic 'Action to perform'.

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 'Create[s] or import[s] a Menese wallet' with specific verbs and resource identification. It distinguishes from siblings (menese_send, menese_balance, etc.) by focusing on wallet initialization rather than operations.

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 maps the three action values to their behaviors (new/generates, import/restores, status/shows), providing implicit usage guidance. However, it lacks explicit when-to-use guidance relative to sibling tools or prerequisites (e.g., whether to check status before creating new).

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 discloses that strategies are 'automated' and explains the behavioral logic of each strategy type (e.g., Stop Loss triggers 'below threshold'). However, it omits operational details such as whether strategies persist until canceled, if funds are reserved upon creation, or what the list/cancel actions return.

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 where every clause earns its place. It efficiently introduces the resource ('Manage automated trading strategies') and immediately specifies the three variant behaviors without redundant verbosity.

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 8 parameters with conditional requirements (e.g., targetPrice only for specific strategies) and no output schema, the description adequately covers the 'what' but leaves gaps on the action types (create/list/cancel) and return values. The 100% schema coverage compensates for parameter details, but the description should ideally acknowledge the CRUD nature of the 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 coverage is 100%, establishing a baseline of 3. The description adds value by defining the semantic meaning of the strategyType enum values (e.g., explaining DCA as 'dollar-cost averaging' and Take Profit as 'sell above target'), which helps the agent map user intent to the correct parameter value.

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 specific verbs ('Manage') and resources ('automated trading strategies') and explicitly lists the three supported strategy types (DCA, Take Profit, Stop Loss). The term 'automated' clearly distinguishes this from sibling tools like menese_swap or menese_send which handle immediate transactions.

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 explains what each strategy type does (e.g., 'sell above target' for Take Profit), providing implicit guidance on when to select each strategyType. However, it lacks explicit guidance on when to use this tool versus immediate execution tools like menese_swap, or prerequisites for creating strategies.

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. It adds valuable execution context via the DEX routing table (revealing which protocols handle which chains), but fails to disclose critical behavioral traits: that this is a destructive financial operation, irreversible on-chain, requires gas fees, or that slippage protection failures result in reverted transactions.

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?

Extremely dense single sentence with pipe-delimited protocol list. Every token earns its place—no filler, immediately front-loaded with action ('Swap tokens'), followed by mechanism ('via DEX'), then specific implementation details. Optimal information density.

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 tool identification given the rich schema, but incomplete for a high-stakes financial operation. Missing: destructive warnings, irreversibility notices, gas fee implications, and failure mode descriptions. The presence of menese_setup as a sibling suggests prerequisites that should be mentioned.

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 baseline is satisfied. The description adds meaningful semantic context by mapping chain parameter values to specific DEX implementations (e.g., EVM chains use Uniswap V3), which helps agents understand execution routing beyond the raw schema enum values.

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?

Specific verb 'Swap' + resource 'tokens' + mechanism 'via DEX' with explicit chain-to-DEX mapping (Uniswap V3, Raydium, etc.). The mention of specific DEX implementations distinguishes this from sibling menese_send (likely simple transfers) and establishes the trading nature of the operation.

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?

Provides no guidance on when to use this tool versus siblings, particularly the ambiguous overlap with menese_quote (which likely fetches prices) while this tool also offers a 'quote' mode. No mention of prerequisites (e.g., menese_setup) or when to prefer quote vs execute modes.

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