AI Agent Tokenized Stock OS

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

With no annotations provided, the description carries full burden. It discloses that the API key is 'shown once', a notable behavioral trait. However, it omits other important behaviors: whether this is a mutation (issuing a key), idempotency, side effects on existing keys, or auth requirements. The description adds some value but is not comprehensive.

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, short sentence front-loaded with key information. It is concise, but the structure could be improved (e.g., listing parameters briefly). Still, it earns its place with no wasted 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?

Given three parameters, no output schema, and no annotations, the description is incomplete. It does not explain the parameters (owner as wallet address, tier as plan selection, txHash as payment transaction) nor the output (how to retrieve the key if shown once). The tool's complexity warrants more detail for an agent to use it correctly.

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 0%, so the description must compensate. It mentions 'ETH payment' but does not explain the three parameters (owner, tier, txHash). The agent gets no guidance on what each parameter means or their relationship to the payment confirmation, leaving ambiguity.

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: after ETH payment confirmation, verify and issue an API key. The verb 'verify and issue' and resource 'API key' are specific. Sibling tools like stocktoken_access_checkout and stocktoken_access_status handle payment and status, so this activation tool is well-distinguished.

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 should be used after ETH payment is confirmed, but it does not explicitly state when to use it versus alternatives (e.g., check status first). No guidance on prerequisites or conditions for use, leaving the agent to infer the sequence.

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. It mentions 'build on-chain ETH payment plan' but lacks detail on behavioral traits such as state mutation, gas costs, failure handling, or permission requirements.

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 concise: two sentences with no filler. Purpose and next step are front-loaded.

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 no annotations, no output schema, and sparse parameter documentation, the description leaves gaps about expected outcomes, errors, and prerequisites. It provides minimal completeness for a 2-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 coverage is 0%, yet the description does not explain the 'tier' or 'owner' parameters beyond implying tier relates to Pro/Team. The enum for tier is not mentioned, nor is the role of owner.

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 clearly states the tool's purpose: building on-chain ETH payment plan for Pro/Team tiers, and specifies the next step to call stocktoken_access_activate. This distinguishes it from siblings like stocktoken_access_pricing or stocktoken_subscribe_plan.

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 clear context for when to use (Pro/Team payment plan) and explicitly instructs the follow-up action (call activate after payment). However, it does not mention when not to use or alternative 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?

The description discloses that pricing is on-chain (ETH, no Stripe) and that the tool explains payment for write tools, which adds behavioral context. However, it does not mention whether the tool is read-only, any authentication needs, or rate limits. Given the lack of annotations, the description provides moderate 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 sentence that is clear and front-loaded with the main action ('List Free / Pro / Team pricing'). Every part of the sentence adds relevant information without wasted 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 simple informational tool with no parameters, no output schema, and no annotations, the description covers the core purpose and some context (on-chain, payment method). It could be more complete by specifying whether the pricing is static or dynamic, but it is largely 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 input schema has zero parameters, so schema_description_coverage is 100%. The description adds value by explaining the output content (pricing tiers and payment mechanism), which is beyond the schema's empty definition. Baseline 4 is appropriate as no parameter details are needed.

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 lists Free/Pro/Team pricing, specifying 'ETH on-chain, no Stripe' and explains it shows how agents pay for write tools. This distinguishes it from siblings like stocktoken_subscription_tiers and stocktoken_fees, as it focuses on pricing rather than just tiers or transaction fees.

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 for retrieving pricing information and payment details, but it does not explicitly state when to use this tool over alternatives (e.g., stocktoken_subscription_tiers, stocktoken_fees). No when-not or alternative tool 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 provided. Description states 'Check' implying a read operation, but does not clarify side effects, authentication requirements, or what happens if access is not paid. For a tool with no annotations, this is insufficient 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?

Single sentence of 13 words, front-loaded with verb and resource. No extraneous 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?

Simple tool with one optional parameter and no output schema. Description covers core function but lacks information about return format (e.g., boolean or object) and what 'paid access' precisely entails. Minimal but meets basic needs.

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 description explains the optional 'owner' parameter by stating it checks 'current API key context or a wallet owner', adding meaning beyond the bare schema (which has no descriptions). More details on format would improve it.

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 'Check' and resource 'paid access', distinguishing from sibling tools like activate, checkout, or pricing. Clearly identifies two contexts: current API key or wallet owner.

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 or not use this tool versus alternatives. The description implies usage for checking paid access status but provides no exclusions or context about 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?

The description implies a read operation ('Preview'), but with no annotations provided, it does not disclose any behavioral traits such as real-time data freshness, caching, idempotency, or permissions required. The tool name suggests a read-only preview, but further details are absent.

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 key action and resources. It is not verbose, but the parenthetical 'vault scaffold preview' adds minor clutter without clear benefit.

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 no output schema and no annotations, the description should provide more detail about the return value (e.g., format, data fields). It only hints at constituents and prices, but an agent would be uncertain about the exact output structure.

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?

There are zero parameters, and schema coverage is 100% (empty schema trivially). According to guidelines, baseline for 0 parameters is 4. The description adds context about what the preview returns, which is adequate.

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 states verb 'Preview' and resources 'AI mega-cap basket constituents' and 'live Chainlink prices', giving a general sense of the tool's function. However, 'vault scaffold preview' is unclear jargon, and the distinction from sibling tools like stocktoken_get or stocktoken_list is not clearly established.

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 stocktoken_get or stocktoken_price. There is no mention of prerequisites, context, or 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 must cover behavioral traits. It discloses non-custodial nature, best venue selection, and limitation to building (not signing/broadcasting). However, it fails to describe what the plan contains, how to execute it, or any side effects (e.g., no mention of gas fees or state changes).

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, each with distinct and valuable information. No filler or redundant phrasing. Front-loaded with core purpose, followed by critical constraints.

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?

Despite no output schema and 9 parameters, the description is extremely brief. It does not explain what the plan output looks like, how to handle the returned plan, prerequisites (e.g., existing approval), or error conditions. Lacks sufficient context for a tool of this complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, meaning the description provides no explanation of any of the 9 parameters. With only required parameters (owner, tokenIn, tokenOut) hinted by names, the description adds no meaning beyond the schema. This is insufficient.

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 clearly states the tool builds a non-custodial transaction plan combining approve and swap, using the best venue (Uniswap/0x). It explicitly mentions it does NOT sign or broadcast, distinguishing it from signing tools. The verb 'Build' and resource 'non-custodial tx plan' are specific.

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?

Description implies usage for preparing a swap plan before signing, and explicitly states what it does not do (sign/broadcast). However, it does not provide explicit guidance on when to use this tool versus siblings like stocktoken_quote or stocktoken_intent_typed_data, leaving the agent to infer.

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; the description indicates a read operation ('Explain') with no mention of side effects, but lacks explicit behavioral disclosure such as read-only or destructive hints.

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?

Description is a single concise sentence that front-loads the purpose, but its brevity sacrifices parameter explanation.

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?

Without output schema or parameter details, the description fails to specify what the explanation returns (e.g., text, decision tree, pros/cons), making it incomplete for an information 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?

The sole parameter 'userIntent' has 0% schema description coverage, and the description adds no meaning or example, leaving the agent without guidance on what value to 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?

Description uses specific verb 'Explain' and names the three alternatives (AI Agent Tokenized Stock OS, Robinhood official Agentic Trading MCP, raw Uniswap/0x), clearly distinguishing it from sibling tools that focus on execution or data retrieval.

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?

Implied that this tool is for routing decisions when selecting between the mentioned platforms, but no explicit when-to-use or when-not-to-use guidance is provided relative to the many 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?

No annotations are provided, so the description carries full responsibility for behavioral disclosure. While 'summarize' suggests a read-only operation, it does not explicitly state that it is non-destructive, requires no special permissions, or any other behavioral traits. The description is adequate but not comprehensive.

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 of 12 words. It directly conveys the tool's purpose without any redundant or extraneous information, earning 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 tool has no parameters and no output schema, the description provides a clear and concise purpose. However, it could be slightly more complete by hinting at the output format or the type of summary (e.g., aggregated totals or individual events), but overall it is sufficient for a simple 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?

There are zero parameters, and schema coverage is 100%. The description adds meaning by specifying what the tool summarizes (AATOS execution fee events and on-chain monetization status) beyond the empty schema. Baseline for zero parameters 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 verb 'Summarize' and the specific resource 'disclosed AATOS execution fee events and on-chain monetization status'. It effectively distinguishes from sibling tools like stocktoken_price or stocktoken_quote, which focus on different 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 for obtaining fee summaries, but it does not provide explicit guidance on when to use this tool versus alternatives, nor does it mention conditions to avoid using it. It lacks exclusion criteria or context-based recommendations.

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 only states the action ('Scan for pools') but does not disclose behavior such as whether it is read-only, requires authentication, has rate limits, or any side effects. The description is too brief for safe agent 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 concise with two sentences, front-loaded with the core action. No filler words, but it sacrifices some necessary 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?

Given the tool's complexity (specific chain, two required params, no output schema), the description is incomplete. It does not mention what the tool returns (e.g., list of pools, details) or any output format. The missing output schema increases the need for description completeness, which is not addressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% (no parameter descriptions in JSON schema). The description mentions 'two tokens' but does not clarify whether tokenA/tokenB should be addresses, symbols, or contract identifiers. This lacks sufficient semantic addition over the empty 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 it scans for Uniswap V3 pools between two tokens on chain 4663, providing a specific verb and resource. It does not explicitly distinguish from sibling tools, but the context suggests it is unique for pool discovery.

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 usage scenario ('Useful when APIs block Stock Tokens'), implying when to use it. However, it lacks explicit guidance on when not to use or how it compares to other tools like stocktoken_quote or stocktoken_liquidity_matrix.

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. Only states 'Get metadata' without disclosing what metadata fields are returned, network behavior, or any side effects. Lacks transparency about the response structure.

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, front-loaded with purpose. No extraneous words. Efficient and to the point.

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 simple lookup tool with one parameter. However, no output schema and no details about the metadata returned. With many sibling tools, more completeness about return value would help 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?

Schema coverage is 100% with clear description for symbolOrAddress. Description adds 'on Robinhood Chain 4663' clarifying the chain, but doesn't elaborate on format beyond what schema says. Baseline 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?

Clearly states verb 'Get metadata' for a specific resource (canonical Stock Token or core asset) by symbol or address, with an example (NVDA) and usage context (verify official before trading). Distinguishes from sibling tools like stocktoken_list (lists many) or stocktoken_price (price-specific).

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?

Explicitly says 'Use to verify a token is official before trading', providing a clear use case. Does not state when not to use or mention alternatives, but the context is sufficient given the sibling list.

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 exist, so the description bears full responsibility. It states the tool builds typed data without disclosing side effects, authentication needs, state changes, or error behavior. It remains vague about what happens during the operation.

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 directly states core function. No extraneous words, very concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has 8 parameters with high complexity, no output schema, and no annotations. Description is too brief, lacking explanation of parameter roles, return value, or operational context. Incomplete for effective 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?

Schema description coverage is 13% (only tokenIn described as 'Symbol or address'). The description adds no parameter information despite low coverage. It does not explain sessionId, owner, amounts, or other required fields.

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 clearly states verb 'Build' and resource 'EIP-712 typed data for an agent trade intent', providing context about offchain authorization. It is distinct from sibling tools that handle execution, pricing, or session management, though it doesn't explicitly contrast with them.

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: create typed data for user signing then on-chain verification. It does not explicitly state when to use this tool versus alternatives or provide exclusion criteria, leaving some ambiguity.

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 burden of behavioral disclosure. It describes the tool as a matrix of routes and implies a read-only query, but does not detail side effects, permissions, or output format. For a simple parameterless tool, this is adequate but not thorough.

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 concise sentences, front-loading the purpose and use case. There is no extraneous information; every word is necessary.

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 no parameters, no output schema, and simple functionality, the description is largely complete. It explains the tool's purpose and usage. A minor gap is the lack of output details, but the name and description together provide sufficient 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 has zero parameters and full schema coverage (100%), so the description does not need to add parameter info. The baseline is 4, and the description adds no confusion, so it earns this 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 clearly states the tool provides a liquidity/route matrix for major USDG pairs on chain 4663, and the use case is to identify which Stock Tokens have live AMM fills. This is a specific verb+resource that distinguishes it from siblings like stocktoken_find_pools or stocktoken_quote.

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 explicitly says 'Use to know which Stock Tokens have live AMM fills,' giving a clear context for when to use this tool. However, it does not mention when not to use it or suggest alternatives, which in context of many siblings would be helpful.

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 burden. It discloses that only registry addresses are real tokenized stocks, which is a key behavioral trait. However, it does not explicitly state whether the operation is read-only or if there are side effects, and the output format is not described.

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 concise at three sentences, with the core purpose front-loaded. It efficiently communicates key information, though it could be slightly more structured (e.g., separate usage notes).

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 no output schema, the description does not explain return values or pagination. The parameter is well-documented, but for a list tool, more context about the response structure would improve completeness. Adequate but not thorough.

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, with the parameter 'kind' already fully described as 'Filter by token kind; default all'. The description adds no additional meaning beyond what the schema provides, so a baseline score 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 verb 'list' and the resource 'canonical tokenized stocks' on Robinhood Chain ID 4663. It specifies the items included (stocks, ETFs, USDG, WETH) and distinguishes from US brokerage equities by directing to a different MCP.

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 explicitly states when to use this tool (AI agents trading tokenized equities/RWAs) and when not to (US brokerage equities, recommending Robinhood Trading MCP). It provides clear context but does not differentiate from sibling stocktoken_ tools like stocktoken_get.

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 present, and the description does not disclose any behavioral traits such as side effects, authentication requirements, rate limits, or performance characteristics. The description fails to inform the agent about the operational nature of the 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 very concise (one sentence), which is efficient, but it lacks structure and key details. It is not particularly well-structured, and brevity comes at the cost of informativeness.

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?

Despite having no parameters and no output schema, the description is insufficiently complete. It does not explain what 'operational metrics' entail, what the 'process' refers to, or how to interpret the output. The agent cannot fully understand the tool's purpose.

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 no additional meaning beyond the schema, but further elaboration is unnecessary as there are no parameters to describe.

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 it provides 'Operational metrics for this AI Agent Tokenized Stock OS process,' which gives a general purpose but lacks specificity. It does not clarify what type of metrics or for which specific process, making it vague but minimally acceptable.

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 its many siblings. There is no mention of use cases, prerequisites, or contexts where 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?

Discloses key trait: 'Does NOT broadcast' and that it involves two-step approve+deposit. With no annotations, this provides basic behavioral context but could elaborate on required prior allowances, reversibility, or on-chain interaction avoidance.

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 captures essence with no fluff. Every word adds value: 'non-custodial', 'ERC-4626', 'deposit plan', 'approve USDG + deposit', 'does NOT broadcast'.

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 no output schema and 4 parameters, the description covers core function and key constraint but omits return value, error handling, parameter dependencies, and usage scenarios. Adequate but leaves gaps for an AI agent.

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 50% parameter descriptions; the tool description adds context about approve+deposit but does not explain individual parameters like 'owner' or 'approveMax'. Partial compensation for schema gaps.

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?

Clearly states the tool builds a non-custodial ERC-4626 deposit plan (approve + deposit) into a specific vault. Distinguishes from sibling withdrawal plan and explicitly notes it does not broadcast, which differentiates it from execution 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?

Implies usage for creating a deposit plan that is not broadcast, but lacks explicit guidance on when to use versus alternatives like stocktoken_execute_plan or subscription tools. No mention of prerequisites or comparison to other planning 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 burden. It indicates a read-only operation but fails to mention potential failure modes (e.g., if wallet not found), authentication needs, rate limits, or any side effects. The behavioral description is minimal.

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 sentence that is both concise and informative, containing no unnecessary 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?

Given no output schema and no annotations, the description should provide more detail about the return format or behavior. It only says 'share balance and underlying USDG', which is vague. The tool is simple but the description is incomplete for an agent to fully understand the output.

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% (1 parameter with description '0x wallet address'). The description adds context that the parameter represents a wallet to read, but does not elaborate beyond the schema. Baseline 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 it reads a wallet's Morpho Earn share balance and underlying USDG, with specific chain 4663. It uses the verb 'read' to indicate a read operation, and the inclusion of 'Morpho Earn (steakUSDG)' distinguishes it from sibling tools like stocktoken_morpho_deposit_plan or stocktoken_morpho_status.

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 (e.g., other read tools or deposit/withdraw plans). There is no mention of prerequisites, typical use cases, or exclusion criteria.

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?

Description discloses it returns address, TVL, and share price. No annotations exist, so description carries full burden; it does not mention side effects or other behavioral traits but is acceptable for a read-only status query.

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, highly concise, no wasted 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 zero-parameter tool with no output schema, the description fully specifies what is returned (address, TVL, share price) and the context (chain 4663, Steakhouse USDG vault).

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?

No parameters; baseline of 4 per rubric, and description adds no parameter info beyond the schema which has none.

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 clearly states it returns status on chain 4663 for the Steakhouse USDG vault, including address, TVL, and share price. However, it does not explicitly differentiate from sibling tools like stocktoken_morpho_position.

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 on when to use this tool versus alternatives; only implies it provides current status.

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 discloses that the tool does not broadcast, which is a key behavioral trait. However, it lacks details on side effects, permissions, or state changes, leaving gaps 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, front-loaded sentence of 16 words. Every word is informative with 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 5 parameters, no output schema, and no annotations, the description is minimal. It does not explain the plan's output format, how to use the result, or relationships with sibling tools like stocktoken_execute_plan, leaving the agent underinformed.

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 0% description coverage and 5 untyped string parameters. The description mentions 'withdraw (by USDG) or redeem (by shares)', hinting at assets and shares parameters, but does not explain any parameter meaning or constraints, failing to compensate for the schema gap.

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 builds a non-custodial plan for withdrawing (by USDG) or redeeming (by shares) from Morpho Earn. It distinguishes itself from siblings like stocktoken_execute_plan by explicitly noting it does not broadcast.

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 'Does NOT broadcast' implies this tool is for planning only, and broadcasting would require a separate tool (likely stocktoken_execute_plan). However, it does not explicitly mention when to use or not use this tool versus 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?

No annotations provided, so description must carry behavioral disclosure. Indicates a 'prepare' action (non-destructive) but does not specify side effects, permissions, or return format. Lacks detail on whether it's read-only or mutating.

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, front-loaded with key action and context. No redundancy or unnecessary 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?

With no output schema, description should hint at return value. It does not, leaving ambiguity. However, it provides chain and flow context. Adequate but could be more complete given tool complexity.

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% with basic descriptions. The description adds value by clarifying token as 'symbol or address' and permitData as 'Optional Uniswap quote.permitData to normalize for signing', enhancing understanding beyond 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?

Description clearly states the tool's action: 'Prepare Permit2 approve + optional typed data' for Uniswap-style flows on a specific chain. It distinguishes itself from siblings by specifying the Permit2 mechanism and chain context.

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 context ('for Uniswap-style flows on chain 4663') but does not explicitly state when to use or avoid this tool versus others like stocktoken_intent_typed_data. No exclusions or prerequisites 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 the burden. It indicates the tool reads policy settings, but it does not disclose any potential behavioral traits like authentication requirements, rate limits, or side effects (though likely none for a read operation).

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 sentence that efficiently conveys the tool's purpose without extraneous words. It is front-loaded with the verb 'Get' and the resource 'agent policy'.

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, no output schema, and is a simple getter, the description is mostly complete. It describes what the tool returns. A minor improvement could mention the output format (e.g., JSON), but it is not critical.

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 is empty, so the description adds meaning by specifying the policy fields returned (max notional, slippage, etc.). With 0 parameters and 100% schema coverage, the baseline is 4, and the description provides useful context.

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 retrieves the current agent policy and lists the specific fields (max notional, slippage, simulate-first, kill switch). This distinguishes it from sibling tools like stocktoken_policy_set and stocktoken_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?

The description implies usage for reading the current policy but does not explicitly state when to use it vs alternatives. Since it's a simple getter with no parameters, the usage is implicit but lacks explicit 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?

The description states 'Update' which implies mutation, but no behavioral details are disclosed. Given no annotations, the description should explain side effects, immediacy of changes, required permissions, or reversibility. It lacks this 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 sentence, which is concise, but it lacks necessary detail. While not verbose, it sacrifices substance for brevity, leaving critical gaps.

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 (6 optional parameters, no output schema, no annotations), the description is severely incomplete. It fails to explain the tool's purpose beyond a high-level update, leaving an AI agent without enough context to invoke correctly.

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 0%, and the description adds no parameter information. The 6 parameters (killed, allowedSymbols, maxNotionalUsd, etc.) are entirely undocumented in the description. The description must compensate but does not.

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 'Update' and identifies the resource as 'session policy guardrails' for the AI Agent Tokenized Stock OS. It clearly distinguishes from siblings like stocktoken_policy_get (retrieve policy) and stocktoken_session_update (update session, not policy).

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, scenarios where it should not be used, or comparative context with sibling tools such as stocktoken_policy_get or stocktoken_session_update.

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?

Discloses that the feed price includes corporate-action multiplier when Chainlink is configured. No annotations present, so description carries the full burden. Could be more explicit about readonly nature, but the context implies a read operation.

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 concise: two sentences, front-loaded with the core action. Every sentence adds value 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 the simple parameter set and no output schema, the description provides adequate context about the tool's purpose and behavioral quirks. Lacks details on return structure, but the tool is straightforward enough that this may not be necessary.

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?

Single parameter 'symbolOrAddress' has 0% schema coverage. Description does not elaborate on the parameter's format or expected values (e.g., whether it accepts address, ticker symbol, or both). The name is self-explanatory but adds minimal value beyond the schema itself.

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?

Clearly states it reads USD price and uiMultiplier for a specific resource (Robinhood Stock Token on chain 4663). Distinguishes from generic price tools and brokerage stock quotes.

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?

Explicitly says 'Prefer this over generic price tools for Stock Tokens' and 'Not for brokerage stock quotes', giving clear when-to-use and when-not-to-use 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?

With no annotations, the description carries the full burden. It explicitly states that the tool returns metadata, implying a read-only, non-destructive operation. The listed contents provide transparency about what is returned.

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?

A single, front-loaded sentence that conveys the complete purpose with no unnecessary words. Every part 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 zero parameters and no output schema, the description is sufficient. It specifies exactly what metadata is returned, which is complete for a simple lookup 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?

There are zero parameters, and schema description coverage is 100% (trivial). The description adds no parameter information, but none is needed. Baseline 4 applies.

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 it returns metadata for specific protocols (Uniswap Universal Router, PoolManager, WETH, USDG, feed sources) on a specific chain. It is a specific verb-resource pair and distinguishes from sibling tools that perform actions like access, pricing, or liquidity.

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 tool versus alternatives. However, its purpose is clear (returning protocol metadata), and siblings have distinct functions, so usage context is implied.

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?

Discloses the multi-venue sourcing order and chain, but lacks details on whether the quote is firm or indicative, authentication needs, rate limits, or side effects. 'Oracle-indicative' suggests indicative pricing but is ambiguous.

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, front-loaded with purpose, and no redundancy. However, the jargon density may reduce clarity.

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 8 parameters, no output schema, and low schema coverage, the description is severely incomplete. It fails to explain what the quote returns, parameter roles, or how to specify inputs.

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 very low (13%), and the description adds no parameter-level information. Agents cannot infer the meaning of tokenIn, tokenOut, amountIn, etc. without further context.

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 it's a multi-venue quote tool, listing Uniswap, 0x, and Chainlink, and the chain ID. It distinguishes from siblings like stocktoken_price (simple price) and stocktoken_simulate (simulation), though not explicitly.

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 on when to use this tool vs alternatives like stocktoken_price or stocktoken_simulate. No explicit when-not or context for selection.

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, description carries full burden. Only mentions persistence to DATA_DIR and non-custodial nature. Missing critical behaviors: authentication requirements, default TTL, side effects, error conditions, or whether sessions are automatically cleaned.

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?

Very short but packs core info. Could be more structured (e.g., bullet points) without increasing length. Some crucial details missing, but not verbose.

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?

Incomplete given the complexity (7 params, no output schema, no annotations). Lacks return value description, side effects, prerequisites, and how to use effectively.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so description must compensate, but it adds negligible parameter meaning. 'Scoped permissions' hints at the permissions parameter, but no elaboration on owner, ttlHours, sessionKey, maxNotionalUsd, allowlistSymbols, maxDailyNotionalUsd.

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 creates a durable agent session with scoped permissions, mentioning persistence to DATA_DIR and non-custodial nature. It distinguishes from sibling tools (e.g., session_kill, session_list, session_update) by the verb 'Create'.

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 on when to use this tool versus alternatives. Missing context like prerequisites, typical scenarios, or when not to use. No mention of session lifecycle or relationship to other session 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, so description should disclose side effects. Only says 'immediate kill' without explaining consequences (e.g., data loss, irreversibility) or requirements (e.g., auth, existence).

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, front-loaded with action and note about immediacy. Earns its place, but could benefit from brief 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?

Lacks details on return value, error conditions, and side effects. Incomplete for a destructive tool with no output schema, especially given many sibling tools.

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 0%. The one parameter (sessionId) is not explained in the description; no hints on format, source, or 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?

Clearly states the action: 'Kill an agent session immediately (kill switch).' The verb 'kill' is specific and distinct from sibling session tools (create, list, update).

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 on when to use this tool over alternatives like session_update. Does not mention prerequisites (e.g., session must exist) or when not to use 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?

No annotations are present, so the description must stand alone. It correctly implies a read operation ('list'), but lacks details on pagination, limits, or behavior when no owner filter is applied (e.g., returns all sessions). Some transparency is provided but not exhaustive.

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 communicates the core function efficiently.

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 list tool with one optional parameter and no output schema, the description covers the essential information: what it does and the filtering option. It does not specify return format, but that is acceptable given the low complexity.

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 single parameter 'owner' is a string with no schema description (0% coverage). The description adds 'optionally filtered by owner', which explains its purpose minimally but does not specify format or semantics beyond that.

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 ('List'), the resource ('agent sessions'), and the optional filtering capability. This distinguishes it from sibling tools like session_create and session_kill.

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 session_create or session_kill. The description does not mention context, prerequisites, or 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 provided, the description carries the full burden of behavioral disclosure. It only states 'update limits/permissions' without detailing side effects, security requirements, or whether changes are reversible. For a mutation tool, 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 brief (6 words), which is concise but fails to convey essential information. Conciseness is valued, but here it sacrifices clarity and completeness.

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 5 parameters, no output schema, and no annotations, the description is severely incomplete. It does not explain return values, session existence requirements, or the effects of different parameter combinations.

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 0%, meaning the input schema has no parameter descriptions. The tool description does not add any meaning to the parameters, leaving agents without guidance on what fields like maxNotionalUsd, allowlistSymbols, or maxDailyNotionalUsd represent. This is a critical gap.

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 it updates limits/permissions on an existing session, distinguishing it from sibling tools like stocktoken_session_create, stocktoken_session_list, and stocktoken_session_kill. The verb 'update' combined with the specific resource 'session' precisely conveys the tool's 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?

No explicit guidance on when to use this tool vs alternatives. The description does not mention when not to use it or provide context about prerequisites. The name implies modification of existing sessions, but this is implicit and not elaborated.

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. It mentions some behavioral aspects (checks performed) but fails to disclose side effects, authentication, rate limits, or whether it's read-only. Significant gaps.

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 is concise, but lacks structure. Could add param details without being verbose. Adequate but not exemplary.

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 no output schema, 7 params with 0% coverage, and many siblings, the description is grossly incomplete. It barely covers what the tool does and offers no help for 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 coverage is 0%, yet description provides no parameter explanations. All 7 parameters, including 3 required, are undocumented in both schema and 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?

The description clearly states the tool simulates/pre-trade checks a tokenized stock swap on chain 4663, listing specific checks (allowlist, policy, multi-venue quote integrity). It uses a specific verb ('Simulate') and resource, distinguishing it from siblings like execute_plan or quote.

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 on when to use versus alternatives. With many sibling tools, explicit context or when-not-to-use is missing. Only implies pre-trade scenario.

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, and the description only mentions that it 'Pays treasury on chain 4663'. It does not disclose whether the action is destructive, requires authentication, or has side effects like modifying existing plans. For a build action, more behavioral context is needed.

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: one for the action and parameters, one for the payment effect. No filler, front-loaded, and every word adds value.

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, no annotations, and 3 parameters (one required). The description covers purpose and options but lacks details on return values, error cases, prerequisites, or idempotency. For a creation tool, this is incomplete.

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 67%. The description adds meaning to 'tier' and 'ethAmount' (e.g., 'preferred over raw ethAmount', custom amount example), which goes beyond the schema. However, the required 'owner' parameter has no description in schema or description, which is a gap.

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 'Build' and the resource 'non-custodial ETH subscription plan', with explicit options for tier (pro|team) or custom ethAmount, and includes the chain ID. This distinguishes it from sibling tools like tip_plan or deposit_plan.

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 tool over alternatives like stocktoken_tip_plan or stocktoken_morpho_deposit_plan. It only implies usage by listing tier vs custom amount, but does not provide context for decision-making.

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 discloses that the tool reads on-chain data and has a deployment condition, but does not describe the return format, cost, or implications of the check.

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 sentence with no wasted words. It efficiently conveys the core action and includes an important deployment 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?

Given the simplicity of the tool (one parameter, no output schema), the description is moderately complete. It states the action and a deployment condition, but lacks information about the output format or possible status values, which would be helpful for an agent.

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 only parameter 'owner' has no description in the schema (0% coverage). The tool description mentions 'wallet' but does not clarify what 'owner' represents (e.g., wallet address) or its required format. The description adds minimal value beyond the parameter name.

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 ('Check on-chain subscription status') and the target ('a wallet'). It differentiates from siblings like stocktoken_subscription_tiers by focusing on status rather than tiers or plans.

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 tool versus alternatives. The deployment requirement is mentioned but not contextualized against other 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 are provided, so the description bears full responsibility. It discloses the tool lists on-chain tiers and the payment method, but does not explicitly confirm read-only behavior, permission requirements, or any side effects. The simplicity of listing a collection partially compensates.

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?

A single sentence with no unnecessary words. It directly conveys the action, resource, and key differentiator. Very concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with no output schema, the description could elaborate on what information the list returns (e.g., tier names, costs, durations). Currently it only says 'subscription tiers' without specifying fields, leaving some ambiguity about the output structure.

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?

Input schema has zero parameters, and schema coverage is 100%. With 0 parameters, baseline is 4. The description adds no param info, but none is needed.

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 'List' and the resource 'AATOS on-chain subscription tiers', and adds distinguishing context 'paid in ETH to treasury. No Stripe.' This effectively differentiates from any Stripe-based alternatives among siblings.

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 tool vs siblings like stocktoken_subscribe_plan or stocktoken_subscription_status. The mention of 'No Stripe' only hints at an alternative, but no direct comparison or exclusion criteria.

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. It reveals that the tool returns several system fields, but does not disclose side effects (likely none), authentication needs, or performance characteristics. Additional context would improve 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?

A single, front-loaded sentence with no wasted words. It efficiently communicates the tool's purpose and output components.

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 tool with zero parameters, no output schema, and no annotations, the description provides a list of fields but lacks detail on output format, data types, or conditional availability. More information would help an agent fully understand 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?

No parameters exist, so schema coverage is 100%. The description adds value by listing the returned fields, which is helpful beyond the empty schema. Baseline of 4 is appropriate for a zero-parameter tool with descriptive return info.

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 'Full system status' and lists components: secrets, venues, chain, version, session count, fees. It distinguishes itself from siblings by covering broad system-level info rather than specific operations or sub-system statuses.

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 tool vs alternatives. The description implies a general status read, but does not specify scenarios, exclusions, or mention other status tools like stocktoken_access_status or stocktoken_morpho_status.

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, description must disclose behavior. It implies a read-only listing but does not explicitly state it’s a query, nor mention permissions, side effects, or rate limits.

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, front-loaded, no filler. 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?

Lacks output schema; description does not explain return format or that it’s a query. Could be improved by stating how the asset list is presented.

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?

Zero parameters; baseline is 4. The description adds value by explaining what the tool returns (accepted assets), compensating for the empty 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?

Description clearly states the tool shows what the tip wallet can accept (ETH, ERC-20, optional BTC) and implicitly distinguishes from sibling tools like stocktoken_tip_plan or stocktoken_tip_presets, though it does not explicitly contrast them.

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 on when to use this tool versus alternatives (e.g., stocktoken_tip_plan, stocktoken_tip_presets). Does not specify prerequisites or context.

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 indicates the tool builds a plan (not executes it) and requires user confirmation. However, it does not disclose side effects, permission requirements, or what happens after building.

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 concise with three sentences, though the formatting of asset options is slightly fragmented. Generally efficient with no wasted 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?

The description covers core functionality, supported assets, and user confirmation, but since there is no output schema, it should describe return value or next steps. This gap reduces completeness.

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 high (83%). The description adds value by specifying ETH as default asset, presenting preset options for ETH, and clarifying the relationship between amount and preset. This goes beyond the schema's field descriptions.

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 indicates the tool builds an optional tip plan, listing supported assets and input options. However, it does not differentiate from sibling plan-related tools like stocktoken_execute_plan or stocktoken_subscribe_plan.

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 mentions user confirmation and non-coercion, but provides no guidance on when to use this tool versus alternatives such as stocktoken_execute_plan. No context for selection among siblings is given.

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 present, so the description fully bears the burden of behavioral disclosure. It reveals that the tool lists accepted assets (ETH, ERC-20 on 4663, optional native BTC) and confirms tips are never required. This is adequate for a read-only listing tool, though auth or rate limit info is absent.

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 sentences long, front-loaded with the main action, and contains no unnecessary words. Every sentence serves a purpose: the first specifies the output, the second clarifies cost policy.

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 parameterless tool with no output schema, the description covers the main points: what is listed and the optional nature of tips. However, it omits details like whether pagination is used or if the list is exhaustive. Still, it is nearly complete given the low complexity.

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 zero properties (100% coverage). The description adds value beyond the schema by explaining what the tool returns: tip presets and accepted assets. The baseline for 0 params is 4, and the description exceeds it by providing clear semantic context.

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 lists optional tip presets (ETH) and accepted assets, using the specific verb 'List' and identifying the resource. It distinguishes from sibling tools like stocktoken_tip_assets by focusing on presets and accepted assets together.

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?

Only minimal guidance is provided: 'Tips never required.' No explicit when-to-use or alternative recommendations are given. The description implies usage for checking tip presets but does not contrast with similar tools like stocktoken_tip_plan.

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 bears full responsibility for behavioral disclosure. It does not mention side effects, read-only nature, required permissions, or response format. The description is too minimal to adequately inform the agent of behavioral traits.

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 sentences long, with no unnecessary words. It is front-loaded with the core action and efficiently adds the intended use case.

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 (two parameters, no output schema), the description covers the basic purpose and use case but lacks details on return values, error conditions, or chain context. It is minimally adequate but leaves gaps.

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 50% (one of two parameters described). The tool description does not add any information about parameters beyond what is in the schema. It fails to compensate for the missing symbols description, leaving ambiguity.

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: 'Value a wallet's Stock Token / ETF / USDG balances on Robinhood Chain 4663.' It uses a specific verb ('Value') and resource ('wallet's balances'), and distinguishes from sibling tools focused on activation, pricing, or metrics by specifying portfolio analysis.

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 includes 'Use for portfolio analysis of onchain RWA holdings,' which provides clear context for when to use the tool. However, it does not explicitly state when not to use it or mention alternative tools, missing the highest standard.

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