CIPHER x402 — Paid Solana & Crypto Tools

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

Without annotations, the description carries the full burden. It discloses update frequency (per release), data quality (hint, cross-check required), and cost (free). It does not mention read-only nature or response format, but the caveats are valuable.

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

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

Three sentences, each adding value: purpose, use case, and behavioral caveats. No redundant or unnecessary phrasing.

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

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

Despite having no output schema or annotations, the description covers purpose, platforms, target users, update frequency, and a usage warning. It lacks specifics on response structure, but for a simple list tool this is sufficient.

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 0 parameters, so the description is not required to explain parameters. Baseline for no parameters is 4. The description adds context about the snapshot's content and sources, which is helpful beyond the schema.

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

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

The description explicitly states it returns a curated snapshot of live audit competitions from specified platforms (Code4rena, Cantina, Sherlock, direct-protocol). It uses a specific verb 'Return' and clearly identifies the resource. No sibling tools compete in this domain.

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 context: useful for solo wardens triaging contests. It doesn't explicitly state when not to use, but no alternatives exist among siblings, making usage clear. Exclusions are not needed.

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 clearly discloses the paywall behavior: without payment, it returns an accept-list; with payment, it returns exposure data. No annotations are provided, so the description carries the full burden. It does not mention rate limits or other destructive actions, but the transparency about the paywall is commendable.

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

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

The description is two sentences long, front-loaded with the core purpose, and efficiently conveys function and payment mechanism without unnecessary words.

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

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

Given no output schema, the description lists specific data returned (open perp positions, collateral, etc.) and explains the two response types. It lacks mention of prerequisites like wallet existence but is generally complete for a simple tool.

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

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

Schema coverage is 100%. The description adds meaning beyond the schema by explaining the _payment parameter's role in unlocking paid responses and mentioning the cost. The wallet parameter is straightforward.

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 checks a Solana wallet's exposure to Drift Protocol, specifying data points like open perp positions and collateral. While it distinguishes from general wallet tools through specificity, it does not explicitly differentiate from siblings like solana_wallet_scan.

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

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

The description explains the payment mechanism and two modes (with/without _payment), but does not provide guidance on when to use this tool over sibling tools such as solana_wallet_scan or solana_wallet_security_audit_rules.

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

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

With no annotations, the description carries full burden. It discloses key behaviors: SHA-1 prefix, k-anonymity, no plaintext sent, payment mechanism, and return of 402 accept-list without payment. It does not detail the response format when payment is provided, but the core behavioral traits are adequately 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?

Four sentences, front-loaded with the primary purpose. Each sentence adds essential information without redundancy or fluff. Efficient and well-structured.

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

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

No output schema is provided, so the description should indicate the return format. It mentions the 402 accept-list for unpaid requests, but does not specify what the paid response looks like (e.g., boolean, count, or match data). This is a noticeable gap, though the tool is simple and the main behavior is covered.

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%, and the description adds meaningful context beyond the schema: it explains that _payment is for signed authorization and what happens if absent, and it clarifies the sha1_prefix purpose in privacy terms. This adds value over the schema alone.

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?

Describes a specific verb and resource: 'Check whether a password hash prefix (SHA-1, first 5 chars) appears in the HIBP breach corpus.' The purpose is unambiguous and distinct from sibling tools, which are unrelated (e.g., audit_comp_live_listings, check_drift_exposure).

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?

Explains the privacy property (k-anonymity, no plaintext sent), pricing, and the two modes of operation (with or without _payment). Provides clear context on how to use the payment parameter, though it does not explicitly exclude alternative tools or scenarios.

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

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

Discloses key behavioral traits: paid tool, payment method (signed x402 v2), behavior without payment (returns 402 accept-list). No annotations exist, so description carries full burden and does so adequately, though rate limits or auth beyond payment are not mentioned.

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

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

Single dense paragraph is front-loaded with main function and covers all key points without redundancy. Minor improvement possible with structured breaks, but highly efficient overall.

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

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

Despite no output schema, description thoroughly details return fields (per-exchange rate, OI, aggregate, divergence, max/min) and explains payment flow. Given the complexity of a paid multi-venue tool, the description is complete and actionable.

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

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

Adds substantial meaning beyond schema: explains symbol as base asset with examples, describes _payment as signed authorization with upstream forwarding. Schema already has full coverage, but description enriches with aggregation context and return data details.

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?

Specifically states it fetches perpetual-futures funding rate intelligence for a base asset aggregated across 17 major venues, clearly distinguishing it from sibling tools which cover unrelated domains (audit, password, food, 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?

Provides clear usage context: intended for perp-arbitrage bots, requires $0.01 USDC payment on Base via x402 authorization. Does not explicitly state when not to use or name alternatives, but the payment and aggregation details guide appropriate use.

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

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

No annotations provided, so the description carries full burden. It discloses that the tool returns 'cleaned latest observations', is priced at $0.005 USDC, and requires a signed x402 authorization. It also explains the behavior without payment (returns 402 accept-list). This is comprehensive for a read operation, though rate limits or error handling are not specified.

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

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

Three sentences, each earning its place: purpose with examples, return characteristics, and payment mechanism. Information is front-loaded, and there is no redundancy. Efficient and clear.

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 lacks an output schema and does not detail the structure of returned data beyond 'cleaned latest observations'. While the tool is simple, for completeness it could mention typical fields or error handling. It does explain payment flow well, but the return format is vague.

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%, but the description adds significant context: examples of series IDs, explanation of the payment flow, and the effect of the '_payment' parameter. This goes beyond the schema's field descriptions, providing practical guidance.

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 fetches a FRED series by ID, with examples (e.g., DGS10, WALCL). The verb 'Fetch' and resource 'FRED Economic Data series' are specific, and it is distinct from sibling tools like coinalyze_funding_rates or pubmed_medical_search.

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 indicates when to use the tool (to fetch a FRED series by ID). It provides examples and a pricing note. While it does not explicitly exclude alternatives, given the diverse sibling tools, this clear context is sufficient. No when-not or alternative tools 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?

No annotations are provided, so the description carries the full burden. It discloses the payment mechanism (x402 v2, $0.25 USDC on Base), the behavior when '_payment' is absent (returns accept-list), and the content type (markdown). It does not mention rate limits or idempotency, but for a premium content tool, the key behavioral traits are covered.

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 four sentences, front-loaded with the main action. Every sentence provides necessary context (available chapters, pricing, payment argument behavior). Zero wasted words or repetition.

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

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

Given the tool's complexity (payment-unlocked content), the description covers the core workflow. It lacks output format details beyond 'markdown', but no output schema is provided. It could mention if there are any additional restrictions or response structure, but for a fetching tool, 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 input schema already describes both parameters with 100% coverage. The description adds value by explaining the purpose of the slug enum (the four chapter titles) and the nature of '_payment' (signed x402 v2 authorization) along with its behavioral impact. This context goes beyond the schema definitions.

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

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

The description clearly states the action ('Fetch') and the resource ('CIPHER premium chapter (markdown)'). It lists the four available chapters via enum, distinguishing this tool from any sibling tool that might offer similar content.

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

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

The description explains two usage scenarios: with a signed '_payment' argument to unlock the paid response, and without it to receive a 402 accept-list. While it does not explicitly mention when not to use the tool or suggest alternatives, the sibling tools are unrelated, so no further guidance is needed.

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 the payment requirement, that the tool returns a health score with breakdown, and the behavior when payment is missing. It does not mention side effects or auth beyond payment, which is sufficient for a read-only operation.

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

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

The description is somewhat verbose, listing specific health factors that could be implied. It is front-loaded with the main purpose, but the additional details on factors could be trimmed without losing meaning.

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

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

Despite no output schema, the description succinctly states the return format (0-100 score with breakdown). The parameters are fully covered, and the payment mechanism is explained, making the tool's usage complete for the given complexity.

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

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

Schema coverage is 100%, and the description adds significant detail for the '_payment' parameter (signed x402 v2 authorization format). The 'repo' and 'owner' parameters are self-explanatory, but the payment explanation enhances clarity beyond the schema.

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

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

The description clearly states the tool's purpose: scoring a GitHub repository's health based on multiple factors like commit cadence, issue latency, etc. It is distinct from sibling tools, which are for other domains.

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

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

The description explains when to provide a payment parameter for paid access and what happens without it. It does not mention explicit alternatives among siblings, but the unique payment model provides adequate guidance.

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

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

No annotations are provided, so the description fully explains the behavior: the tool is paywalled ($0.01 USDC), and without a valid '_payment' it returns a 402 accept-list. This is a key behavioral trait disclosed. However, it does not mention side effects or state changes (though likely none).

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: four sentences, each providing essential information. It front-loads the main purpose and then details inputs, outputs, and payment. No redundant or vague statements.

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, but the description states 'Returns tip lamports + EV breakdown', which is sufficient for an agent. The payment flow is thoroughly explained. Some detail on the format of the EV breakdown could be added, but overall it's complete enough.

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%, but the description adds substantial meaning: it clarifies units (USD for pool_depth and expected_profit), the range for slot_prob [0..1], and the behavior of the optional '_payment' parameter (unlocks paid response). This goes far beyond the schema descriptions.

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

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

The description clearly states the tool's function: 'Compute an expected-value-maximizing Jito tip for a Solana arbitrage bundle.' It specifies the verb 'compute', the resource 'Jito tip', and the domain 'Solana arbitrage bundle'. This distinguishes it from sibling tools which are unrelated.

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 lists inputs (pool_depth, expected_profit, slot_probability) with units and range, and explains the payment mechanism (x402 authorization). It does not compare to alternatives, but the specialized nature makes use clear. No explicit exclusions are given, but 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?

No annotations provided. The description discloses behavioral traits: returns data for last 12 months, searches multiple name types in parallel, payment mechanism, and the 402 accept-list behavior. Missing rate limits or auth details beyond payment, but still 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?

Five concise sentences with no redundancy. First sentence captures core function, followed by search details and payment info. Efficiently structured and 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?

With no output schema, the description adequately explains return values (top reactions, report count, seriousness breakdown). Three parameters are well-documented, and payment flow is clear. Complete for a simple lookup tool.

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

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

Schema covers 100% of parameters with descriptions. The description adds value beyond schema: explains parallel search behavior, default limit (10), and the effect of _payment parameter. No gaps.

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

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

The description clearly states the tool performs an openFDA drug adverse-event lookup, returns top reactions, report count, and seriousness breakdown, and searches across multiple name types. No sibling tools overlap in domain, making purpose 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 provides explicit guidance on payment: priced at $0.005 USDC, must pass '_payment' argument to unlock response, otherwise tool returns 402 accept-list. However, no explicit 'when to use vs alternatives' is given, but siblings are unrelated so not critical.

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?

Given no annotations, the description fully discloses behavior: output format (lat/lon, address block, match_quality), pricing ($0.001 USDC), payment mechanism (x402 v2), and the fallback behavior (returns 402 accept-list if no payment).

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 four sentences covering purpose, output, pricing, and payment behavior. Every sentence adds necessary information with no redundancy or fluff.

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

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

For a simple two-parameter tool with no output schema, the description adequately covers input, output, pricing, and payment behavior. It lacks mention of error cases or rate limits, but these are not critical for basic usage.

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

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

Schema description coverage is 100%. For the `_payment` parameter, the description adds significant detail beyond the schema (x402 v2, base64-encoded EIP-3009 authorization). For `q`, it provides an example address, which adds context beyond the schema's one-line description.

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

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

The description clearly states the tool performs forward geocoding via OpenStreetMap Nominatim, converting an address string to lat/lon, normalized address block components, and a match_quality label. It distinguishes from sibling osm_reverse_geocode by its forward geocoding nature.

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 implicitly indicates it is for forward geocoding and mentions the payment requirement, but does not explicitly state when to use versus alternative tools (e.g., osm_reverse_geocode) or provide guidance on when not to use.

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

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

With no annotations, the description carries full burden. It discloses the payment dependency (+ x402 authorization) and the conditional response behavior (paid response vs 402 accept-list). It adds value beyond the schema by explaining the tool's operational context, though it omits details like rate limits 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 three sentences with no redundant phrases. It efficiently conveys purpose, payment flow, and state without payment. However, the sentence on pricing could be integrated more succinctly.

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 lacks output schema and only vaguely describes the return as 'normalized address + place class/type.' The structure of the 402 accept-list response is not detailed. Given no output schema, the agent would benefit from more explicit return format and limitation 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%, but the description adds meaning beyond parameter names. It explains that 'lat' and 'lon' are WGS84 coordinates for reverse geocoding toward a normalized address, and it clarifies the '_payment' parameter's role in the x402 payment flow. This significantly aids parameter understanding.

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 'Reverse geocoding via OpenStreetMap Nominatim' with a clear verb-resource pair. The phrase 'lat/lon → normalized address + place class/type' specifies the input-output mapping. Given sibling 'osm_geocode' likely does forward geocoding, this tool is well-distinguished.

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

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

The description clearly explains when to include the '_payment' argument to unlock paid response and what happens without it. It provides context for the payment flow but does not explicitly state when to choose this tool over alternatives like 'osm_geocode' or when not to use it.

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

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

With no annotations, the description fully discloses the payment mechanism (pricing, required authorization for paid response, and the fallback behavior returning a 402 accept-list). It also describes the enriched output structure. No other behavioral traits (e.g., rate limits) are mentioned, but the key behavioral aspect (payment) is well-covered.

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 five sentences, each adding value: purpose, output, use case, pricing, and payment behavior. Front-loaded with the main action. No redundancy.

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

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

Given the tool's complexity (payment, no output schema), the description covers the core functionality, output fields, and payment workflow. Missing details like error handling or empty response, but these are minor for a search tool. Overall 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?

Schema coverage is 100%, so baseline is 3. The description adds value by describing the return format (list of fields, enrichment block) which is not in the input schema. It also clarifies the purpose of the '_payment' parameter beyond the schema description. This extra context elevates the score.

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

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

The description clearly states the tool searches PubMed for medical/life-sciences literature, a specific verb and resource. It also mentions the enriched output, making the purpose unambiguous. No similar sibling tools exist, so differentiation is not needed.

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 identifies the tool as 'Ideal for medical RAG agents,' providing a clear use case. However, it does not explicitly state when not to use it or mention alternatives, though sibling tools are unrelated.

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 the critical payment-gated behavior: without '_payment' it returns a 402 accept-list, with it returns findings. It does not explicitly confirm read-only status, but the scan nature implies safety. The pricing and referral CTAs are also noted.

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 three concise sentences, front-loaded with the core purpose, followed by pricing and payment instructions. No unnecessary words.

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

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

Given no output schema, the description lists the types of findings (portfolio value, dust accounts, etc.) and mentions referral CTAs, giving a reasonable picture of the response. However, it could be more explicit about the format or structure of the findings.

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

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

Schema coverage is 100%, so baseline is 3. The description adds contextual value for '_payment' by explaining the consequence of missing it and the need for a signed authorization, which goes beyond the schema description.

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

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

The description clearly states the tool scans a Solana wallet for specific findings (portfolio value, dust accounts, stale stake accounts, low-liquidity warnings) and returns findings plus CTAs. This distinguishes it from sibling tools like solana_wallet_security_audit_rules which likely focus on security audits rather than portfolio health.

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 scanning a Solana wallet for the listed issues but does not provide explicit guidance on when to use this tool vs alternatives, nor does it mention exclusions or prerequisites beyond the payment mechanism.

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

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

No annotations are provided, so the description carries full burden. It states the tool returns metadata and is free, indicating a read-only operation with no side effects. However, it does not explicitly confirm no destructive behavior 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 long sentence that lists many anti-patterns, making it somewhat dense. While informative, it could be more concise or structured (e.g., a bullet list) for 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 tool has no parameters, no output schema, and no annotations. The description states it 'returns metadata' but does not specify what the metadata contains (e.g., list of rules, version details). This lack of detail leaves the agent unsure of the return value.

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 no parameters (0 params, 100% coverage). Per guidelines, 0 params gives a baseline of 4. The description adds no parameter information because none are needed, but it does add context about the ruleset version and scope.

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 returns metadata for a specific ruleset (cipher-solana-wallet-audit v1.4.0) and lists specific anti-patterns it catches. It distinguishes from sibling tools like solana_wallet_scan by focusing on metadata of a ruleset rather than actual scanning.

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

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

The description mentions the tool is free but does not provide explicit guidance on when to use this tool versus alternatives like solana_wallet_scan. It implies usage for obtaining ruleset information but lacks when-not or alternative 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?

No annotations are provided, so the description carries full burden. It explains the output format (macro block plus alternates), the payment requirement ($0.002 USDC via x402), and the two response modes (paid vs. accept-list). It does not specify error handling or empty results, but the payment flow is well disclosed.

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 four sentences, each serving a distinct purpose: identification, output details, pricing, and payment mechanism. It is front-loaded and contains no redundant 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?

Given the absence of an output schema, the description adequately details the return values (macro block and alternates) and the conditional behavior based on payment. It does not cover error cases or the structure of the accept-list, but the essential information for tool usage is present.

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

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

Schema coverage is 100% with descriptions for each parameter. The description adds value beyond the schema by explaining the purpose of 'limit' (controls number of alternates, default 5) and emphasizing that '_payment' unlocks the paid response. This enriches the agent's understanding.

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 starts with 'USDA FoodData Central nutrition lookup', clearly stating the verb (lookup) and resource (food nutrition data). It further specifies that it handles both brand and generic foods, and there are no sibling tools in the same domain, so differentiation is not needed.

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

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

The description implies the tool is for nutrition queries on any food, but it does not provide explicit when-to-use or when-not-to-use guidelines, nor mention alternative tools. With no related siblings, the lack of explicit usage context is acceptable but not ideal.

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