AgentDataHub Gateway

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 focuses almost entirely on cost savings and free credits, but does not explain how the tool decides between chat, image, or deep-reasoning based on the prompt, what the response format is, or whether there are any side effects. This is a significant gap for an unannotated 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 long, promotional, and packed with emojis, ALL-CAPS, pricing details, and savings claims. The core function is buried among marketing noise. It is not front-loaded or structured clearly, making it harder for an agent to quickly parse the essential information.

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

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

There is no output schema, so the description should explain what the tool returns. It does not describe the response format, how to interpret results from different task types, or how routing between chat/image/deep-reasoning works. The description is incomplete for a tool that serves multiple modes and returns unspecified 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%, so the baseline is 3. The description repeats the wallet info already present in the schema (free credits, 100 anonymous, 5000 bound wallet) and adds no new semantic meaning to the parameters. It adds marginal value by saying 'Pass prompt' but the schema already documents both parameters well.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the tool is an AI gateway for chat, image, and deep-reasoning tasks, and also provides real-time data. It distinguishes itself from sibling data-fetching tools by being a general-purpose AI endpoint. However, the purpose is somewhat clouded by heavy marketing language and pricing focus, making it less crisp than it could be.

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 tells users to 'SWITCH your data API to this gateway' for free data, and indicates it handles chat/image/deep-reasoning prompts. This provides clear usage context and a rationale for choosing this over other data APIs. It does not explicitly name alternatives or give when-not-to-use guidance, but the context is sufficient.

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 bears the full burden. It clearly discloses the key behavioral trait: without payment, an x402 402 payment challenge is returned, and wallet enables the free trial/paid path. It does not mention error/return formats, but the payment behavior is a material and well-communicated detail.

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 conveys purpose, the optional wallet parameter, and the payment-challenge behavior without waste. Every clause earns its place.

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

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

For a simple two-parameter fetch tool with no output schema/annotations, the description is adequate but not fully complete. It explains the payment gate but does not describe the successful response shape or how to discover the id (e.g., via list_products), leaving some ambiguity for the 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 description coverage is 50%: wallet is described, id is not. The description adds payment and trial meaning for wallet and implies id identifies the data product, but id's format and requirement remain under-specified. It partially compensates for the low schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific action ('Fetch a data product') with a clear resource and the relevant id/wallet context. It does not explicitly differentiate from siblings like get_product_info or list_products, but 'fetch' and the payment challenge make the data-delivery purpose clear.

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 gives usage context around wallet and payment ('Pass wallet... to use the free trial / paid access; without payment... challenge is returned'), but it does not state when to prefer fetch_data over sibling tools or list exclusions. Usage is implied rather than explicitly contrasted.

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

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

No annotations are provided, so the description must carry the burden. It discloses that the tool is 'Free' and mentions the inclusion of payment instructions (x402, USDC), but does not describe the response format or any permissions needed. For a simple get operation, this is adequate but not rich.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single efficient sentence with an additional 'Free.' indicator. Every word contributes to understanding the tool's purpose and cost, with no redundant or filler content.

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 one parameter and no output schema, the description adequately conveys what the user receives: product details and payment instructions. It could clarify the structure of the response, but given the tool's simplicity, it is sufficiently complete.

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

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

The schema already fully describes the 'id' parameter with an example ('econ-fred'), and the description only repeats 'by id.' Since schema coverage is 100%, the description adds no additional semantic value, so the baseline score of 3 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 the tool's function: 'Get details and payment instructions... for one product by id.' It uses a specific verb ('Get') and identifies the resource ('product'), and the scope ('one product by id') distinguishes it from sibling tools like list_products.

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 use case—when you have a specific product id—which differentiates it from listing tools. It does not explicitly name alternatives or provide exclusions, so it's clear but not exhaustive.

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 carries the burden. It discloses that the listing is 'Free' and what fields are returned, which are important behavioral traits. However, it does not mention potential pagination, rate limits, or any response format details beyond field names.

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 with no superfluous words. Every element (what, where, fields, free) is purposeful and immediately useful.

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

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

For a parameterless list tool with no output schema, the description sufficiently covers what the tool returns and that it is free. It lacks details like ordering or size limits, but these are minor for a catalog listing and do not impede correct use.

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, so the schema already fully communicates the input. The description does not need to add parameter meaning, and it appropriately focuses on the return payload.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb 'List' with a clear resource 'all pay-per-call data products on AgentDatum' and explicitly states the output fields (id, price USD, description). This distinguishes it from sibling tools like get_product_info, which likely targets a single product.

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 description does not mention any use cases, exclusions, or relationships to sibling tools, leaving the agent to infer that this is for browsing the catalog.

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 disclosing behavioral traits. It does mention the cost (Price 0.05 via x402) and free tier (wallet), which is beyond schema info. However, it lacks details on the exact response format, data freshness, or any potential side effects. The truncated sentence ("<=25 i") also leaves part of the threshold behavior unclear.

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 reasonably sized but contains a truncated sentence ("<=25 i") and a somewhat run-on structure. It starts with a generic 'Finance Signal Bundle' prefix that could be trimmed. The information is not presented as efficiently as it could be, but it's not overly 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?

The tool is simple with one optional param and no output schema, so the description should explain what is returned. It indicates the value is a percentage and gives interpretation thresholds, which is helpful. However, it does not specify the exact return format (e.g., JSON structure, timestamp), nor does it fully complete the threshold explanation due to truncation. With no output schema, the description should provide more complete return info.

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 one optional param 'wallet' with a complete description covering the free tier, so schema description coverage is 100%. The tool description adds no additional parameter semantics, which is acceptable given the schema already handles it, hence baseline 3.

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 provides a live computed altcoin season index, with specific details about the calculation (percentage of top 50 coins excluding stablecoins outperforming BTC over 30 days) and thresholds (>=75 indicates altseason). This clearly distinguishes it from the many sibling signal 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?

It implies when to use (to get altcoin season data) but does not explicitly state when to use it over alternatives, nor does it mention any exclusions or alternative tools. Given the large number of sibling signals, explicit guidance would be beneficial, but the description's clarity about the metric provides some implicit usage 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 burden of disclosure. It mentions real-time delivery and a price of 0.01 via x402, which are useful behavioral cues. However, it does not state whether any payment is required upfront, what happens without a bound wallet, or the format of the returned data.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences and front-loaded with the core purpose. The first sentence efficiently describes the data delivered; the second adds use case and pricing. It loses a point due to the typo 'shipping d Price'.

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

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

Given the tool's simplicity (1 optional param, no output schema), the description covers the essential return values (BDI level and % changes), use case, and cost. It is complete enough for an agent to select and invoke the tool, though it could mention the response format.

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% for the single optional 'wallet' parameter, which is well described in the schema. The description adds no new parameter-specific meaning beyond what the schema already provides, so baseline 3 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 'get live computed signal' for the Baltic Dry Index (BDI), including the specific data points: level and daily/monthly/yearly % change. This is a specific verb+resource and distinguishes it from sibling tools like processed_commodity or processed_net_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?

It explicitly identifies the use case: 'A leading indicator for global trade and bulk commodity shipping.' This provides clear context for when to use the tool, though it does not explicitly name alternatives 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?

With no annotations provided, the description carries the full burden. It adds useful behavioral context: 'no key' (no API key needed), pricing via x402 (payment required), and wallet-based free tier. This goes beyond a simple data-fetch description, though it does not describe output format or side effects. The garbled 'A sample of emerging ma' slightly reduces clarity.

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 short and front-loaded with the core purpose, but it contains a truncated, confusing phrase ('A sample of emerging ma Price 0.01') that undermines clarity. It could be more concise and well-structured if completed and cleaned up, but as written it is somewhat awkward.

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?

Although there is no output schema, the description lists the specific data returned (Selic, IPCA, USDBRL), which helps. It also includes pricing and access details. However, it does not describe the format of the result, error handling, or how the payment integration works beyond a vague x402 reference, leaving gaps for a complete understanding.

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 one optional parameter 'wallet' with a description covering its free-tier purpose. Schema coverage is 100%, so the baseline is 3. The tool description does not add any additional meaning about the wallet parameter beyond what the schema states, so no bonus is warranted.

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: 'get live computed signal: Brazil macro snapshot' with specific data points (Selic, IPCA, USDBRL). This differentiates it from sibling tools by focusing on Brazil-specific macro data, meeting the bar for a specific verb+resource+scope.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for Brazil macro signals by naming the specific indicators, but it does not explicitly state when to use this tool vs alternatives or provide exclusions. No alternative tools are mentioned, so it relies on the reader to infer context from the name and content.

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

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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It discloses the data source (mempool.space, real-time, no key) but introduces an unexplained pricing element ('Price 0.01 via x402 (USDC on Base)') without clarifying execution behavior, side effects, or return format. The truncated 'unconfirmed tran' adds further ambiguity.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single run-on sentence that mixes signal metrics with a pricing note, making it difficult to parse. The phrase 'unconfirmed tran Price' appears truncated and the structure is messy, not concise or well-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?

There is no output schema, so the description must explain return values; listing metrics partially does so, but the final metric is cut off and no units or structure are given. It also fails to explain the wallet parameter's role in pricing or the x402 mechanism, leaving significant gaps for a tool with no annotations.

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

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

The schema covers the only parameter (wallet) with a description, achieving 100% coverage. The tool description adds no additional parameter context, so the baseline score of 3 is appropriate given the schema's adequate documentation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it provides a live computed BTC network health signal with a specific verb 'get' and lists concrete metrics (total hashrate, mining difficulty, mempool backlog, recommended fees). However, the trailing 'Price 0.01 via x402' confuses the purpose and doesn't cleanly distinguish it from other processed_* siblings beyond naming the BTC chain.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies this tool is for BTC network health data by listing relevant metrics and stating 'mempool.space real-time, no key'. It does not mention when not to use it or point to alternative tools, providing only implicit guidance 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?

Since annotations are absent, the description carries the transparency burden. It discloses that the signal is 'live computed', uses 'China data via AkShare', and costs '0.05 via x402 (USDC on Base)'. It does not explicitly state read-only behavior or side effects, but the context implies a data retrieval operation with a pricing mechanism.

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, information-dense sentence. It front-loads the core purpose, then adds data source and pricing details without unnecessary fluff. Every word contributes 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?

Given the tool's simplicity (one optional parameter, no output schema), the description is sufficiently complete: it defines the signal, data source, cost, and the metric's importance. It does not describe the return format, but the metric itself ('spread in bp') is clear enough for an agent to understand the expected 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?

The input schema provides a detailed description for the only parameter 'wallet', including free-tier credit details. With 100% schema coverage, the description adds no additional parameter semantics, 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 tool's purpose: 'get live computed signal: US 10Y minus China 10Y yield spread in bp'. The verb 'get' and the specific resource (US-China yield spread) make it distinct from sibling tools like processed_us_yield, which focuses on US yields only.

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 labels the signal as a 'key macro cross-border capital flow metric', which tells the agent when to use it (for cross-border capital flow analysis). However, it does not explicitly mention when not to use it or name alternative tools, so it lacks explicit exclusion or alternative 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 transparency burden. It discloses 'live computed', 'updated daily', and 'Price 0.01 via x402 (USDC on Base)', which are useful behavioral traits. However, it omits details about the free tier (already in schema) and does not explain what happens if the wallet is absent or the exact nature of the live computation (e.g., cached, delayed).

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 composed of two tight, front-loaded sentences. It efficiently communicates the tool's purpose, output scope, update frequency, and pricing without unnecessary 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?

For a tool with one optional parameter and no output schema, the description covers the key aspects: the output (index 0-100), the underlying assets, update cadence, and cost. It lacks explicit return format details, but the index range implies the numerical response. The sibling differentiation is clear enough overall.

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

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

Schema description coverage is 100% for the single 'wallet' parameter, which already explains the free tier and bound wallet credits. The tool description adds no additional meaning beyond that, so the 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 explicitly states 'get live computed signal' with a specific resource ('Composite pressure index (0-100) from WTI/Brent crude, gold, and silver'), which clearly distinguishes it from sibling tools like signal_gold or processed_energy. The word 'Bundle' further clarifies its aggregate scope.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives such as signal_gold or processed_energy. It mentions update frequency and pricing but does not state scenarios where a combined commodity index is preferred or when to use a single-commodity signal instead.

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

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

No annotations are provided, so the description must carry the behavioral burden. It discloses the data source (mempool.space), self-calculation, and mentions payment via x402 (USDC on Base), but the payment statement is ambiguous and the return format is not specified. This is partial 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 run-on sentence that mixes the signal purpose, EMA band list, and payment details without punctuation or clear structure. The tail 'EMA bands [9/14/25/40/60/90/128/20 Price 0.01 via x402' is confusing and poorly organized.

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?

While the core purpose is clear, the description omits the output structure (what the signal actually looks like) and leaves the payment/cost aspect ambiguous. With no output schema or annotations, the description should be more explicit about return value and usage conditions.

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

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

Schema description coverage is 100% (the 'wallet' parameter is documented in the schema with its free-tier explanation). The description does not add parameter information, but the baseline of 3 applies because the schema fully covers the only parameter.

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 gets a live computed signal for BTC Hashrate Ribbon (difficulty ribbon equivalent), self-calculated from mempool.space daily hashrate. This specific verb+resource distinguishes it from sibling signal tools like processed_altseason or processed_bdi.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage when a BTC hashrate/difficulty ribbon signal is needed, but it does not explicitly provide when-to-use guidance or alternatives. It relies on the tool name and sibling names to convey distinction.

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 burden. It adds value by disclosing the cost (Price 0.01 via x402 on Base) and source (Farside), but it does not mention side effects, rate limits, or whether it is read-only. This partial transparency 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 sentence that front-loads the core purpose and includes necessary cost information. It is generally concise, though the run-on structure and typo ('outf' instead of 'outflow') slightly 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?

The description lists the main computed fields and mentions the payment requirement, which helps set expectations. However, without an output schema, it does not clarify the return format or resolve the truncated phrase 'top inflow/outf', so the completeness is moderate.

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, 'wallet', is fully described in the schema with 100% coverage, including its optionality and free-tier details. The description adds no further parameter-specific meaning beyond what the schema already provides.

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 live computed Bitcoin spot ETF net flows from Farside, enumerating specific data points (single-day net inflow, total, 5-day cumulative, top inflow/outflow). It is resource-specific but does not explicitly contrast with sibling signal tools, so it is clear but not fully differentiated.

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 about when to use this tool versus alternatives, and no exclusions or prerequisites are mentioned. The description simply describes what the tool does without contextualizing its use case.

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 disclose behaviors. It mentions pricing (0.01 via x402 on Base) and intraday validity, which are useful. However, it omits details such as whether wallet binding affects output, what response format is returned, and any rate limits or authentication 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?

The description is a single sentence that packs the signal type, source, scale, validity, and pricing. Every word contributes meaning, and it is front-loaded with the core 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?

For a paid tool with no output schema or annotations, the description covers the core signal and pricing but lacks details on the x402 payment flow, the free tier wallet behavior, and expected return shape. These gaps could hinder an agent's 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?

The single optional 'wallet' parameter is fully described in the schema (100% coverage), so the baseline is met. The description does not mention this parameter, but the schema already explains its purpose and free tier implications.

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 live cross-asset fear gauge (0-100) synthesized from VIX, gold/equity/crypto volatility, valid intraday. This specific verb+resource (get signal) and detailed scope distinguish it from generic sibling tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives no guidance on when to use this tool versus alternatives like processed_vix_stress or signal_market_stress. It only describes the product's nature without specifying selection criteria 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?

No annotations are provided, so the description must disclose behaviors. It mentions 'via x402 (USDC on Base)' but does not explicitly state that this is a paid transaction, whether wallet authorization is required, what the response contains, or any rate limits. The phrase 'Measures bond Price 0.01' is cryptic and fails to clarify the pricing/metering mechanism.

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 short (two sentences), but the second sentence ('Measures bond Price 0.01 via x402 (USDC on Base)') is ambiguous and confusing, potentially wasting valuable context. It does not clearly earn its place and may mislead an agent about pricing or output.

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

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

This is a paid financial signal tool with no output schema and no annotations. The description explains the signal calculation but omits essential context: what the response looks like, how payment works, whether a wallet must be provided for paid access, and any prerequisites. The cryptic pricing reference is insufficient.

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 (wallet) is fully described in the input schema (coverage 100%), including free-tier options. The tool description adds no further semantic detail about the wallet parameter; the mention of x402/USDC is tangential and not clearly linked to the parameter.

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 a specific action ('get live computed signal') and a precise resource ('MOVE volatility proxy (bond market VIX)') with a detailed formula ('30-day rolling annualized volatility of 10Y Treasury yield (DGS10) from FRED'). This distinguishes it from sibling processed_* tools that focus on other signals.

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 when bond-market volatility (MOVE proxy) is needed, but it does not explicitly state when to use it over alternatives or provide exclusion criteria. No sibling tools are named as comparisons.

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 useful behavioral traits: the data is lagged 1 day, sourced from BGeometrics, and computed live. It also attempts to disclose a fee ('Price 0.01 via x402 (USDC on Base)'), but the phrase is confusingly worded with a typo ('Cycle-leve'), obscuring the actual payment mechanism. No annotations are present, so this limited disclosure carries full weight, but the ambiguity prevents a higher score.

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 relatively compact, but it contains a typo ('Cycle-leve') and an unclear clause that requires interpretation. The three-sentence structure is front-loaded with the core signal, but the final sentence's wording detracts from overall 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?

For a simple one-parameter signal tool, the description covers the key elements: metric definition, source, latency, interpretation thresholds, and a pricing hint. However, it does not describe the return value shape or what 'Finance Signal Bundle' includes, and the payment detail is garbled, leaving some gaps in the absence of an output schema and annotations.

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

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

The schema already fully describes the only parameter (wallet) with a clear explanation of its free-tier benefit. The description adds no parameter-level semantic nuance, so the baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's function: getting the live computed BTC MVRV (market cap / realized cap) signal from BGeometrics with a 1-day lag. It specifies the exact metric and interpretive thresholds, distinguishing it from the many sibling processed_* and signal_* tools. The verb 'get' and resource 'BTC MVRV signal' are specific and unambiguous.

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 thresholds (MVRV<1 buy zone, >3.5 bubble top) provide concrete context for when this signal is actionable, implying its use as a BTC valuation/cycle indicator. However, it does not explicitly name alternative tools or scenarios where a different signal would be preferred, so it falls short of a 5.

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

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

No annotations are provided, so the description must carry the full burden. It discloses the live computed nature and the exact formula, and mentions a cost of 0.05 via x402 (USDC on Base), hinting at a fee. However, it does not specify output format, latency, error behavior, or any side effects, leaving 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?

The description is a single dense sentence that packs the formula, context, and pricing. It is front-loaded with 'Finance Signal Bundle - get live computed signal'. However, the phrase 'c Price 0.05' is cryptic and could be a typo, slightly hurting 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?

There is no output schema, and the description does not explain what the returned signal looks like beyond the formula. It gives the computation and a high-level use case, but lacks details on response structure or caveats, making it minimally viable but 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 description coverage is 100% for the single parameter 'wallet', with full details already in the schema. The description adds no additional parameter semantics, so baseline 3 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 the tool's function: 'get live computed signal: Fed net liquidity = Fed balance sheet (WALCL) - reverse repos (WLRRAL) - Treasury General Account (TGA)'. It provides a specific verb, resource, and formula, and frames it as a 'global risk asset pricing anchor', distinguishing it from sibling processed_* signals.

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 usage is clear: it is for tracking Fed net liquidity as a risk asset pricing anchor. However, there is no explicit guidance on when to use this versus other processed_* tools, nor any exclusion criteria or alternatives 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 exist, so the description must disclose behavioral traits. It mentions data lag (1 day) and source, but the payment/cost aspect is ambiguous: 'Price 0.01 via x402 (USDC on Base)' is unclear whether 'Price' is an output or a fee, and the typo 'anc' further obscures meaning. This ambiguity is significant for a tool that might charge users, and there is no clear statement of whether authentication or wallet is required at the tool level.

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 and relatively short, but the final clause is confusing due to the typo 'anc' and the ambiguous 'Price 0.01 via x402' phrasing. It is not as clean or well-structured as ideal.

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 the signal source, lag, and interpretation thresholds, but lacks a clear statement of what the return value looks like (e.g., numeric value, JSON object). More importantly, the payment requirement is muddled; for a paid API call, the cost/usage should be unambiguous. With no output schema, the description should compensate more.

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

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

Schema description coverage is 100%, so the baseline is 3. The description does not mention the 'wallet' parameter, but the schema already provides a clear description including free tier credits, so the description need not compensate. No additional parameter meaning is added.

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 a live computed BTC NUPL signal, identifies the specific resource (BTC NUPL) and source (BGeometrics), and distinguishes it from sibling tool by naming the exact metric and its interpretation. The verb 'get' and resource 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?

The description gives clear context by explaining NUPL thresholds for sentiment interpretation (capitulation zone, bubble top), implying use cases for market sentiment assessment. It does not explicitly mention alternatives or when not to use, but the context is strong enough for a signal-specific tool.

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

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

With no annotations provided, the description carries the full burden. It does add value by explaining the calculation method (self-calculated from CoinGecko data) and pricing (0.01 via x402). However, it does not disclose the return format, potential errors, or any side effects beyond being a read-only signal.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, with the main purpose front-loaded and pricing/calculation details following. It is efficient, though 'Finance Signal Bundle' is slightly redundant with the specific nature of the tool.

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 read-only signal tool with one optional parameter, the description covers the core functionality well but omits the output shape. Since there is no output schema, the agent is left guessing what the response looks like. It also doesn't mention any dependencies or potential latency.

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%—the single 'wallet' parameter is already fully described in the schema. The tool description adds no further info about this parameter, so the baseline score of 3 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 'get live computed signal' for 'BTC Puell Multiple', with a formula and data sources. This distinguishes it from sibling tools like processed_mvrv or processed_nupl by specifying the exact indicator and asset.

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 intended use is implied by naming the Puell Multiple indicator, but there is no explicit guidance on when to use this tool versus alternatives, no recommended scenarios, and no exclusions. It relies on the indicator name to convey usage.

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 carries full burden. It discloses the pricing (0.01 USDC via x402 on Base) and live computation nature, which are key behavioral traits. It lacks rate-limit or side-effect details, but for a read-only signal tool this is adequate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the core purpose, and every phrase adds value (signal type, interpretation thresholds, cost/access). 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 tool with a single optional parameter and no output schema, the description covers purpose, interpretation, and cost effectively. Minor gap: it doesn't describe the response format, which is relevant given no output schema, but the simple nature of the tool mitigates this.

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% and the wallet parameter is fully described in the schema. The description adds no additional parameter-specific semantics beyond the overall pricing context, which indirectly relates to wallet usage but is not explicit. 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?

Description clearly states it 'get[s] live computed signal' for the Put/Call volume ratio on SPY options, specifying the exact resource and a contrarian interpretation. The specificity distinguishes it from the many sibling finance signal tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage context through the contrarian indicator definition and thresholds (>1.2 panic, <0.8 greed), which tells the agent when this signal would be relevant. However, it doesn't explicitly mention when to use this over siblings or provide 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 are provided, so the description bears the full burden. It discloses that the signal is live computed and self-calculated from CoinGecko, and mentions the 0.01 cost via x402, adding behavioral context. However, it does not describe return format, error behavior, or any prerequisites beyond the schema.

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 short but poorly structured: the second sentence is a run-on with a typo ('scarci') and mixes signal context with pricing, making it harder to parse. Not every sentence earns its place.

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

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

For a simple tool with one optional parameter and no output schema, the description explains the signal's purpose and cost but does not explain what the response contains or how the wallet parameter affects usage. The missing output format is a significant gap given no output schema exists.

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

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

The only parameter (wallet) is fully described in the schema, so the baseline is 3. The description does not add any parameter semantics beyond the schema, though it mentions cost which is unrelated to the wallet parameter.

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 explicitly states it provides a live computed BTC Stock-to-Flow signal, self-calculated from CoinGecko, which clearly distinguishes it from sibling tools that cover other indicators. The mention of 'Finance Signal Bundle' adds slight ambiguity, but the core purpose is unambiguous.

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 the many sibling signal tools (e.g., processed_fear, processed_mvrv). The description only implies it's for BTC S2F but does not state exclusions or 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 are provided, so the description carries the full burden. It discloses the price (0.01 via x402) and intraday validity, which are important behavioral traits. However, it does not mention the free-tier credits (though the schema does), potential failure modes, or the return structure beyond the 0-100 range.

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, each earning its place: the first defines what the signal is and its inputs, the second provides price and validity. No redundant or filler content.

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 one-param tool with no output schema, the description covers the signal's nature, composition, range, validity, and price, which is largely sufficient. It omits practical payment-flow details and output format, but the wallet schema supplies free-tier context, making it reasonably complete.

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

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

The schema description covers 100% of the single optional 'wallet' parameter, explaining the X-Wallet free tier and credits. The description text itself adds no parameter-specific meaning, so 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 the tool 'get live computed signal' with a specific resource: 'Institutional momentum index (0-100) from gold, global equities, and US macro signals.' This is specific and distinguishes it from sibling processed_* tools by calling it a 'Finance Signal Bundle' and describing a composite index.

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?

Usage context is implied by the description (e.g., 'valid intraday' suggests short-term use), but there is no explicit guidance on when to use this tool versus alternatives like other processed_* tools or signal_* tools. No exclusions or alternative names are mentioned.

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

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

With no annotations, the description carries the full burden. It discloses that the signal is 'live' but 'lagged 1 day' and mentions a price of 0.01 via x402 (USDC on Base), which adds behavioral context. However, it does not describe the output format or any potential side effects, leaving 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?

The description is front-loaded with the core purpose, but the second sentence becomes garbled ('capitulation/a Price 0.01 via x402'), which reduces clarity and structural quality. It is not as clean as it could be.

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 low complexity (1 param, no output schema, no annotations), the description covers the essential purpose and interpretation. However, it lacks details about the return value structure and the ambiguous 'a Price' statement leaves a gap, making it only minimally viable.

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% (the single optional 'wallet' parameter has a full description). The tool description adds no additional parameter semantics, so the baseline score of 3 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 'get live computed signal: BTC SOPR' from BGeometrics, with a specific metric and interpretation. This distinguishes it from sibling processed_* tools, which cover different indicators.

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?

Usage is implied by the specific BTC SOPR metric, but no explicit when-to-use or alternatives are mentioned. The description lacks exclusion criteria or comparison to other processed_* 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 the full burden of behavioral disclosure. It mentions the signal is 'live computed' and includes a price, but it does not disclose output format, how the score is delivered, any rate limits, or whether a wallet is required. The description is incomplete and even contains a truncated word ('rati') that obscures behavior.

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, but it is not well structured due to a typo ('rati Price' likely missing 'o') and an unnecessary 'Finance Signal Bundle' prefix. It is somewhat front-loaded with the action, but the flow is disrupted and would benefit from clearer punctuation or separate sentences.

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

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

With no output schema and no annotations, the description should explain what the caller receives beyond the score range. It does not mention the output shape, how to interpret the composite score, or how the optional wallet affects access. The description appears cut off, leaving out important contextual information for a paid 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 input schema provides 100% coverage for the only parameter (wallet), including its optional nature and free-tier advantages. The tool description adds no parameter-specific semantics; the price note is not tied to a parameter. Baseline 3 is appropriate since schema already explains the parameter.

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 function with a specific verb ('get') and resource ('live computed signal'), and specifies exactly what it computes: a composite risk score (0-100) from four named factors. This distinguishes it from sibling tools like processed_fear (single factor) and other processed_* signals.

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. It only describes what the signal is and mentions the price, but does not suggest scenarios, prerequisites, or exclusions. There is no comparison to other signal tools in 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 are provided, so the description carries the burden. It does disclose important behavioral traits: daily updates, validity ('valid for days'), and a price of 0.05 via x402 (USDC on Base). However, it doesn't explicitly state that this is a read-only operation or describe potential side effects, though 'get live computed signal' implies safety.

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 brief but the second sentence is awkwardly phrased: 'valid for days' is ambiguous and could confuse an agent. The first sentence is clear and front-loaded, but the second sentence lacks structure and 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?

For a simple tool with one optional parameter and no output schema, the description adequately covers the returned data (yields, spread, curve status), update frequency, and cost. The ambiguity around 'valid for days' is a minor gap, but the core context is complete.

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

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

The schema description for the single 'wallet' parameter is thorough (covers free tier and credits), and schema coverage is 100%. The tool description adds no additional meaning about the parameter beyond what the schema already provides, so the 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 identifies the tool as a finance signal provider for US 10Y/2Y yields, 2s10s spread, and curve status. The verb 'get' and specific resource distinguish it from the many processed_* sibling tools, and it notes it's a key macro trading metric.

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?

Usage context is implied by the description ('key macro trading metric'), but there's no explicit guidance on when to use this tool versus alternatives like processed_commodity or signal_gold. No exclusions or alternative tool references are provided.

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

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

No annotations are provided, so the description carries the full burden. It discloses a cost ('Price 0.01 via x402 (USDC on Base)') and the live computed nature of the signal. However, it does not explicitly state that the operation is read-only, mention rate limits, or describe potential side effects. For a simple data retrieval tool, this is adequate but not fully transparent.

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 short but poorly structured. The second sentence 'A thermometer for US stock marke Price 0.01 via x402 (USDC on Base)' contains a typo ('marke' instead of 'market') and awkwardly combines a metaphor with pricing information. This reduces clarity and professionalism, making it less effective than a concisely written description.

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 provides enough information about the output (VIX level and classification with thresholds) to be actionable. It lacks an explicit output format example, which could be useful, but given the simple nature of the tool and the presence of a well-documented parameter, the description is mostly complete. The typo and fragmented ending slightly undermine 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?

The input schema fully describes the sole parameter 'wallet' with context about free credits, so the schema coverage is 100%. The description adds no additional meaning about parameters, but since the schema is comprehensive, the baseline of 3 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 states the tool 'get live computed signal' and specifies 'Real-time VIX level and volatility stress classification' with thresholds. This clearly identifies the primary purpose and is distinct from sibling tools like processed_fear or signal_market_stress. However, the phrase 'Finance Signal Bundle' is slightly ambiguous, and the garbled ending 'US stock marke Price 0.01 via x402' introduces minor confusion.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for VIX-related volatility stress assessment via classification thresholds, but it does not explicitly state when to use this tool over alternatives or mention any exclusions. Sibling tools exist for similar market stress signals, yet no guidance is provided for selecting among them.

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 the price (0.01 via x402) and that the signal is 'live computed', but does not disclose whether the call is read-only, any side effects, or failure behavior. The wallet parameter mentions a free tier, but the main description doesn't explain the payment flow beyond price.

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: two sentences that front-load the core purpose and follow with pricing. Every word earns its place, and there is no redundancy with the schema or annotations.

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 tool with one optional parameter and no output schema, the description covers the data source, signal types, historical range, and pricing. It does not describe the return format, but for a 'signal' tool the agent can reasonably infer a numeric or data payload. Slightly more detail would be ideal, but it is adequate.

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

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

The input schema fully documents the sole optional 'wallet' parameter with 100% coverage, including its purpose (X-Wallet free tier). The description adds no new parameter semantics, so the baseline score of 3 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 what the tool does: 'get live computed signal' with specifics on the signal type (Quantile and momentum) and data source (World Bank global GDP series, over a decade). This clearly distinguishes it from sibling signal_* tools by its global GDP focus.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage when global GDP quantile/momentum signals are needed, but provides no explicit when-to-use or alternative guidance. It does not contrast with sibling tools like signal_macro_us or signal_global_indices, so usage context is only 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?

No annotations are provided, so the description must fully disclose behavioral traits. It mentions 'live computed signal' and data granularity (48-96 hourly points), but the clause 'reflecting European Price 0.01 via x402' is cryptic and does not clearly explain if the tool incurs costs, whether it is read-only, or what the output structure looks like. This leaves significant ambiguity.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single run-on sentence with awkward phrasing (e.g., 'reflecting European Price 0.01' with a double space). It tries to convey too many elements in one breath, making it less scannable than a structured two-sentence format would be.

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, the description should explain what the returned signal looks like and clarify the pricing mechanism. It does neither clearly. It also omits any mention of the optional wallet parameter, which is part of the free tier context. The description is adequate for basic purpose but incomplete for a tool with a possible payment component.

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 describes the only parameter (wallet) with detailed information about free tier credits, achieving 100% schema description coverage. The description adds no parameter-specific meaning, but the baseline of 3 is appropriate given the schema's thoroughness.

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 function: it provides live computed signals (momentum/quantile/volatility) for spot electricity prices in Finland, Sweden, and Denmark. The specific geographic scope and signal types distinguish it from sibling tools like signal_energy or signal_macro_us.

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 electricity price signals but lacks explicit guidance on when to use this tool versus alternatives. It does not name any sibling tools or provide exclusion criteria, leaving the agent to infer suitability from the geographic and commodity-specific 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?

No annotations are present, so the description carries the behavioral disclosure burden. It discloses cost via 'Price 0.01 via x402 (USDC on Base)' and indicates it is 'live,' but it omits the free tier option mentioned in the schema and does not describe the return format or payment failure behavior. This is partial transparency, not misleading but incomplete.

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 and immediately states the purpose and pricing. Every word adds value, with no fluff or repetition of the tool name.

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 schema (1 optional param) and no output schema, the description still leaves gaps: it does not specify the return format or the free-tier option that the schema mentions. The cost detail is good, but the missing free-tier nuance and vague output description reduce 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 description coverage is 100% for the only parameter (wallet), which fully explains its purpose and free-tier options. The tool description adds no parameter-specific information, so the baseline of 3 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 uses a specific verb ('get') and clearly defines the resource: live computed momentum signals and price trends for WTI, Brent, natural gas, and gasoline. It distinguishes from sibling tools by listing exact energy commodities and specifying 'live computed' signals, setting it apart from processed data tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description clearly implies usage: use this when you need momentum signals and price trends for these specific energy commodities. It does not explicitly name alternatives or exclusions, but the context is clear, so it earns a 4 rather than a 5.

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 pricing (0.05 via x402) and output structure (trend, factor breakdown), but does not mention side effects, authentication requirements beyond the wallet param, rate limits, or error behavior. It is somewhat transparent but not fully.

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 run-on sentence with an awkward prefix 'Finance Signal Bundle -' and a truncated item 'med' (likely media/medical) that is unclear. It packs many details but lacks clear structure, making it less concise than it could be.

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?

There is no output schema, so the description must explain return values. It partially does (score range, trend, factor breakdown) but does not give an example response format or clarify ambiguous terms like 'med'. It also lacks guidance on error cases or authorization nuances beyond the wallet parameter. Adequate for a simple tool but with 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?

The input schema has 100% description coverage for the single optional 'wallet' parameter, so the baseline is 3. The tool description adds no additional parameter semantics; it does not even mention the wallet parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly identifies the tool as retrieving a live geopolitical tension score (0-100), including a 90-day trend and five-factor breakdown. This distinguishes it from sibling signal tools (e.g., signal_gold, signal_energy) by naming the exact metric and components.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no explicit guidance on when to use this tool versus alternatives, such as other signal_* tools. The usage is only implied by the metric name (geopolitical risk), with no mention of use cases, exclusions, or sibling comparisons.

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 discloses that the tool costs 0.05 via x402 (USDC on Base) and provides live signals, which is important behavior. However, it lacks details on authentication, rate limits, or response shape, leaving some transparency 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?

The description is two sentences: the first clearly states the tool's purpose, and the second gives pricing. It is concise, front-loaded, and contains 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?

For a straightforward signal retrieval tool with one optional parameter and no output schema, the description adequately explains what the user gets (momentum/percentile signals for 11 indices) and the cost. It could be more explicit about the return format, but overall it is complete for the tool's 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 only parameter (wallet) is fully documented in the schema with details on free tier credits, so the schema carries the semantic load. The description adds no parameter-specific information, and the baseline of 3 applies due to 100% schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it fetches live computed momentum and percentile signals for 11 named global indices (e.g., Nikkei, DAX, FTSE, Hang Seng), distinguishing it from sibling signal tools that target other markets or asset classes.

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?

It positions the tool as providing a 'quick global market strength view,' which gives clear context for when to use it. It does not explicitly name alternatives, but the use case is specific enough to guide 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?

With no annotations provided, the description carries the full burden. It discloses the paid nature (0.05 via x402) and that signals are live/computed with a 30-day trend. However, it omits details like output format, rate limits, or payment flow, leaving significant behavioral aspects opaque.

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, front-loaded with the core function, and includes essential pricing information. No wasted words or redundant details.

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

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

The tool has a simple schema and no output schema, but the description does not explain the output data structure or how to interpret the signals, which an agent would likely need. Payment and scope are covered, but return values are not, leaving a completeness gap.

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 optional wallet parameter is fully described in the schema, including free tier details. The description adds no additional parameter semantics, but schema coverage is 100%, so the 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?

Clearly states it provides live computed signals for COMEX gold and silver futures, specifying signal types (quantile/momentum/volatility) and a 30-day trend. This distinguishes it from sibling signal tools focused on other markets, though the vague term 'bundle' slightly dilutes specificity.

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 use when gold/silver futures signals are needed and mentions the payment requirement, but it does not explicitly contrast with sibling tools or state when not to use it. No alternatives are named, so guidance is implied rather than explicit.

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 transparency burden. It discloses critical pricing (0.01 USDC via x402) and indicates the signal's nature as momentum/quantile. While it doesn't describe output structure or error behavior, the price and live-computation detail add meaningful behavioral context beyond the input schema.

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 covering purpose and price. No filler words or redundant restatements of the tool name; every clause contributes to understanding the tool's function and cost.

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

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

Given the tool's simplicity (one optional parameter, no output schema), the description adequately covers the core purpose, data source, and pricing. It lacks explicit output format details, but for a straightforward signal provider this is a minor gap not unexpected at this complexity level.

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

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

Schema description coverage is 100% for the single optional 'wallet' parameter, so the baseline is 3. The description itself adds no additional parameter details, but since the schema already documents the wallet's free-tier behavior, no further compensation 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 that the tool retrieves a live computed finance signal derived from US unemployment and labor statistics. This distinguishes it from sibling signal tools focused on other domains like gold or energy, making its purpose specific and unambiguous.

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 when to use the tool: when a live labor/momentum signal is needed. Although it doesn't explicitly exclude alternatives or name sibling tools, the domain specificity (US unemployment) provides clear context for selection among the sibling signal_* 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 the full transparency burden. It discloses that the signal is 'live computed' (vs. cached) and explicitly mentions a price of 0.05 via x402 (USDC on Base), which implies a payment side effect. This goes beyond the schema or annotations, though it omits details like auth flows or data freshness.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, front-loaded sentence that quickly states the core purpose ('get live computed signal'), then provides necessary specifics (series list, price). No fluff or redundancy – every word contributes.

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 is adequate for a simple tool with one optional parameter, but it lacks details about the output structure (no output schema exists) and is internally inconsistent by claiming '8 major US macro series' while listing only six categories. This partial ambiguity could leave an agent uncertain about what to expect.

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

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

The input schema describes the single 'wallet' parameter with 100% coverage, including the free-tier explanation. The description adds no additional parameter semantics beyond what the schema already provides, so the schema carries the full burden and the baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses the specific verb 'get' and identifies the resource as a 'Finance Signal Bundle' with clear scope ('8 major US macro series'), listing concrete series like GDP, CPI, unemployment, etc. This distinguishes it from sibling signal tools that focus on other domains (energy, gold, stock reports, etc.).

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 clearly implies it covers US macro signals, which helps an agent select it for that purpose. However, it provides no explicit when-to-use or when-not-to-use guidance, nor does it name alternatives among the many sibling signal tools, leaving the agent to infer usage from the title and listed series.

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

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

No annotations are provided, so the description must disclose behavioral traits. It reveals the live/computed nature, the scale, and the payment requirement. However, it fails to mention the optional wallet for free tier, creating a potentially misleading impression that payment is always required, and does not describe response format or member details.

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 packs substantial detail: what is returned, the scale, the assets, the cost, and the payment method. It is efficient, though the opening phrase 'Finance Signal Bundle' is somewhat redundant and there is a double space issue. Overall, well-structured for its length.

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 one optional parameter and no output schema, the description explains the core output (stress index and member details) and the pricing. However, it omits details about how to use the free tier (the wallet parameter) and what exactly 'member details' includes, leaving some gaps for an agent to infer.

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

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

Schema description coverage is 100% for the single optional parameter (wallet), so the schema fully explains its purpose. The tool description adds no additional meaning beyond what the schema provides, warranting the baseline score of 3.

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: getting a live computed multi-asset composite stress index (0-100) from z-scores of 9 major global assets, indicating overall market heat/cold. This specific verb+resource+scope differentiates it from sibling signals like signal_gold or signal_econ_global.

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 clear context that this is a broad composite stress index, implying use for overall market conditions, but it does not explicitly state when to use it vs. alternatives or mention the free tier option described in the schema. The cost mention (0.10 via x402) adds usage context, but the omission of free credits limits 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 burden. It discloses that the signal is 'live computed' and mentions a price of 0.05 via x402 (USDC on Base), indicating a cost/access mechanism. However, the 'Positive g Price' phrasing is ambiguous, and it does not clarify whether the optional wallet parameter relates to payment or free-tier limits, leaving important behavioral traits unclear.

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 short (two sentences) and front-loaded with the main purpose, but the 'Finance Signal Bundle' intro is vague and the second sentence has a confusing, possibly garbled phrase ('Positive g Price') that reduces clarity. It is not as clean or efficient as it could be.

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, the description lists metrics but does not explain the response format or structure. The payment and wallet interactions are unclear, and there is no guidance on how this signal differs from siblings. The tool appears simple (one optional param), but the output is likely complex, and the description leaves gaps in understanding the full 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?

Schema coverage is 100% for the single 'wallet' parameter, with a detailed description of the free-tier credits. The tool description adds no parameter information beyond that, so the baseline score of 3 applies; the description does not need to compensate.

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 provides a live computed signal for gamma exposure on SPY/QQQ/IWM options chains, listing specific outputs like net GEX, gamma flip level, call/put gamma walls, and put/call OI ratio. This distinguishes it from sibling signal tools by underlying assets and metrics. However, the phrase 'Positive g Price 0.05 via x402 (USDC on Base)' is confusing and detracts from clarity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit when-to-use guidance or alternatives are provided. The purpose is implied by the content (options gamma signal), but with many sibling signal tools, the description does not explain when to choose this over others like processed_put_call or signal_market_stress. It merely describes the tool's contents without usage 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 provided, the description bears full responsibility for disclosing behavior. It reveals that the signal is 'live' (computed in real-time), includes '24 points history', and costs '0.01 via x402 (USDC on Base)', which are meaningful behavioral traits. However, it does not describe the result format, error behavior, or any rate limits, leaving significant 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 run-on sentence with disjointed clauses and a clear truncation ('power g Price'), making it poorly structured. While it packs several pieces of information, the lack of segmentation and the broken ending undermine readability and conciseness.

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

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

The tool has no output schema, so the description should clarify return values, but it only loosely mentions 'signal' and 'history'. It also fails to explain the payment flow implied by 'Price 0.01 via x402' and does not clarify the truncated 'power g' warning. The description is incomplete and would leave an agent uncertain about the tool's full behavior and 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?

The schema already documents the single optional 'wallet' parameter with its own description, achieving 100% coverage. The tool description does not mention the wallet parameter or add any further semantics, but with high schema coverage the 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 identifies the tool as providing a live computed financial signal based on geomagnetic Kp index, with a specific verb ('get') and resource ('live computed signal'). It distinguishes itself from sibling signals by focusing on solar activity's impact on markets/infrastructure. However, the truncated phrase 'power g' and the inclusion of pricing details slightly muddle the core purpose, preventing a perfect score.

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 monitoring solar activity impacts on communications and power infrastructure, which provides a context for when to call this tool. However, it does not explicitly state conditions for use or mention alternative sibling tools, so the guidance is only implicit rather than explicit.

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 burden. It does disclose the one-time fee and price (0.05 via x402 on Base), which is important. However, it doesn't explain the payment flow, what happens without a wallet, or whether the fee is mandatory, leaving ambiguity.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a run-on sentence that mixes product contents with pricing, contains a typo ('an Price'), and is not well-structured. It could be split into clearer sentences for better readability.

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 lists the report contents well, but for a paid tool with a single optional wallet parameter, it doesn't explain how payment is collected or what happens if no wallet is provided. The output schema is absent, so more operational detail would be expected.

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% for the single optional wallet parameter, so the baseline is 3. The description adds no extra meaning about the parameter beyond what the schema already says about the X-Wallet free tier.

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 live computed signal and a full research pack for a stock, listing specific contents (quotes, technical indicators, short interest, options chain). It distinguishes from macro-oriented sibling tools by focusing on individual stocks, though it doesn't explicitly name alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance is given on when to use this tool versus the many sibling signal_* tools. The phrase 'full research pack on a stock' implies a use case, but there are no exclusions, prerequisites, or alternative tool mentions.

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 burden of behavioral disclosure. It transparently reveals the paid nature (0.05 via x402 USDC on Base) and the optional free tier for wallet-bound users, which is critical for an agent to anticipate costs and prerequisites. However, it does not describe the exact response structure 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?

The description is two sentences, front-loaded with the core purpose, and every phrase adds value: signal types, examples, trends, price, and payment method. There is no filler or repetition beyond a slight redundancy in 'Finance Signal Bundle'.

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?

While the description mentions the signals and trends, there is no output schema, and the expected response format is not described. For a paid tool, an agent might need to know whether the output is an array, a JSON object, or includes timestamps. The description gives enough to infer purpose but not enough to fully invoke and parse 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?

The only parameter (wallet) is fully described in the schema with its free-tier details. The tool description adds the cost context but does not add new meaning beyond the schema. Baseline 3 is appropriate since schema coverage is 100%.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly identifies the tool as a live signal bundle for US mega-cap stocks, listing specific signal types (Momentum, volatility, z-score, percentile) and example tickers (Apple, Microsoft, Nvidia, Tesla). This is specific enough to distinguish it from sibling tools like signal_global_indices or signal_gold.

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 use for US mega-cap equity signals but does not explicitly state when to choose this over alternatives such as signal_stock_report or processed_* tools. There is no mention of exclusions or specific use cases, so guidance is implicit rather than explicit.

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