Concierge Intel

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

There are no annotations, so the description carries the behavioral disclosure burden. Listing is inherently read-only, and the description makes that clear. It doesn't explicitly state 'no side effects' or mention auth/rate limits, but the nature of a catalog is transparent enough.

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 and well-structured, with all key information packed into one sentence plus a clear directive. No redundancy or unnecessary detail.

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

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

Given the low complexity (one optional parameter, simple listing), the description is complete. It specifies the contents (prices, paths, curl hints) and the usage context, making it sufficient for an agent to decide when and how to call it.

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

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

The single parameter 'prefix' is fully described in the schema with its optional filter values (intel | security). The description does not add additional meaning 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 states the tool's purpose: listing paid tools with prices, HTTP paths, and curl hints. It also differentiates itself from sibling tools by being a catalog, and the phrase 'Call before paying' adds a clear usage context.

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

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

The instruction 'Call before paying' is a direct usage guideline, telling the agent when to invoke this tool. It also implies this is for discovering paid tool information, which is a distinct usage scenario.

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

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

With no annotations provided, the description carries the transparency burden. It discloses that the call is free, returns a live challenge, and uses base64 encoding. It does not detail error cases or side effects, but for a read-only payment prep this is sufficient.

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, focused sentence. It front-loads the key fact that it is free, then succinctly describes the output and purpose without unnecessary padding.

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 tool with no output schema, the description covers the main points: what it returns, when to use it, and the target resource kind. It could mention what to do after payment, but that is not essential for invoking the tool correctly.

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

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

The schema already documents 'kind' with examples; the description adds context that the kind refers to a paid tool resource, reinforcing the parameter's purpose. This adds meaningful nuance beyond the basic 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 verb 'return' and the object 'a live x402 PAYMENT-REQUIRED challenge', and explains it is for settling a paid tool before tools/call. It distinguishes itself from sibling data/scan tools by being a payment preparation step.

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 it ('before tools/call') and that it is free, but does not explicitly mention when not to use it or alternative payment flows. The temporal context is clear enough for an agent to decide when to call 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?

The description discloses payment-related behavior: unpaid calls return PAYMENT-REQUIRED and omitting paymentSignature yields a challenge. However, the core behavior of the tool (what it does, side effects, or error modes) is entirely opaque because the purpose is 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 a single run-on sentence mixing pricing, endpoint, default body, and payment details. It is not front-loaded with the tool's purpose and lacks clear structure, making it harder to parse quickly.

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 omits any explanation of the tool's output, return format, or how it fits into the broader system. With no output schema and a vague purpose, the context is severely incomplete for an agent deciding whether and how to call it.

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 covers all 5 parameters with descriptions, so schema coverage is 100%. The tool description adds no extra semantic value beyond what the schema already provides—it only references the default body and payment fields indirectly.

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 does not clearly state the tool's function. It mixes pricing, endpoint, and a cryptic default body ('Solana desk A2A orchestration') without explaining what 'A2A pipeline' actually does. There is no verb describing the action or resource.

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 given on when to use this tool compared to the many sibling intel_* tools. It does not mention alternatives, selection criteria, or scenarios where this pipeline is appropriate.

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

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

The description discloses the cost ($0.10 USDC/USDG/USDT or TCX credits), the behavior for unpaid calls (returns a payment challenge), and free-tier options (SOON holder). It does not mention rate limits or side effects, but the payment and challenge mechanics are well explained.

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 dense but organized with clear sections for the endpoint, default body, and payment parameters. It is not excessively verbose, though the repetition of payment-related terms slightly increases 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?

The description covers the essential context: cost, endpoint, default body, payment flow, and free-tier alternatives. It lacks an output schema and does not describe the expected success response format, but given the absence of an output schema, it provides sufficient information to invoke the tool correctly.

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

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

Each parameter in the schema has a description, and the description adds context beyond the schema, such as indicating that paymentSignature should be omitted to receive a structured payment challenge and explaining the credit wallet and holder wallet options. This goes beyond mere parameter listing.

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 verb ('intel-airdrop'), the resource (an HTTP POST to a defined endpoint), and the cost/payment mechanism. It also provides a default body and payment options, making the tool's purpose unmistakable.

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 concrete usage instructions, including the endpoint, default body, and how to handle payment signatures and credit wallets. It lacks explicit guidance on when to prefer this tool over sibling intel tools, but the operational details are sufficient for most use cases.

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 behavior. It does disclose that unpaid calls return a payment challenge and that payment is required, which is relevant. However, it doesn't describe what the tool returns, side effects, or operational details beyond payment, leaving a gap for a paid API call.

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 block combining pricing, endpoint, default body, and payment options. It is concise but poorly structured, with no breaks or clear separation of concerns, making it harder to parse quickly.

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 API call with no output schema, the description is incomplete. It fails to explain what a 'desk brief' contains, what the response looks like, or what an agent should expect. This is a critical gap for an agent deciding whether to invoke it.

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 explaining the default body, clarifying that paymentSignature can be omitted to get a payment challenge, and mentioning creditsWallet and soonHolderWallet as alternative payment paths. This exceeds the schema's basic parameter 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 names the resource 'desk brief' and the endpoint, but does not clearly state what the tool does—e.g., 'retrieve a morning intelligence briefing.' It implies a daily summary but focuses on pricing and payment mechanics, leaving the actual function vague.

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

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

No guidance on when to use this tool versus the many sibling intel tools. It doesn't say 'use for a daily overview' or 'use when you need a consolidated briefing.' The agent must infer purpose from the name and default message.

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 transparency burden. It does disclose the payment requirement, cost, and 402 response for unpaid calls, and mentions a free tier via SOON holder headers. However, it does not explicitly state side effects or whether the operation is read-only, though the intel namespace suggests a non-destructive query.

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

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

The description is dense and mixes cost, endpoint, default body, and payment variants in a single run-on style without a clear lead purpose statement. It is not excessively long but lacks a clear structure and front-loaded intent.

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 specify what a successful response contains. It only describes the default request body and payment-failure behavior, leaving the actual returned data and success criteria undefined.

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 descriptions cover all 5 parameters, including paymentSignature behavior and wallet header mappings. The tool description adds no extra parameter context beyond what the schema already provides, 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 focuses on payment mechanics, endpoint URL, and default body rather than clearly stating what the tool does. The phrase 'Potential exchange listings' in the default body hints at the purpose, but the actual function and output are not explicitly described.

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 sibling intel_* tools, nor when to choose paymentSignature, creditsWallet, or soonHolderWallet. The description only conveys payment mechanics, not use cases 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?

The description discloses one behavioral trait: unpaid calls return PAYMENT-REQUIRED accepts with accepted payment methods. However, it does not describe what happens on a successful paid call, what data is returned, or any side effects. With no annotations, the description carries the full burden, and this is insufficient.

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

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

The description is short but jumbled: it mixes pricing, endpoint, default body, and payment behavior in a single run-on sentence. It is front-loaded with the name and cost, but the lack of structure makes it harder to parse. It is not egregiously long, but the information is not organized effectively.

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 5 parameters, one nested object, no output schema, and 19 siblings, the description is severely incomplete. It does not explain the tool's purpose, return format, or when to use it, so an agent cannot make an informed decision to call it.

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 parameters are fully documented in the schema. The main description adds no extra meaning beyond what the schema already provides—it only mentions the default body {} which is already in the schema's body parameter default.

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 restates the name 'intel-macro' and gives payment details (cost, endpoint, default body) but never states what the tool does. There is no verb or resource indicating the actual function—it could be a generic macro intelligence endpoint, but that is left to inference from the name alone.

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

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

No guidance on when to use this tool versus any of the 19 sibling tools. It does not specify a use case, scenario, or conditions that would select intel_macro over intel_tvl, intel_verdict, etc.

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 transparently reveals that unpaid calls return a structured payment challenge, lists supported payment methods (USDC, USDG, credits, holder wallet), and includes header hints via parameter descriptions. This goes beyond basic annotation-level transparency and clarifies the payment flow.

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 packs endpoint, cost, default body, and payment behavior into a single, dense but compact sentence. It is not overly verbose and stays focused, though the payment details make it slightly cluttered.

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 includes critical integration details (endpoint, payment challenge, accepted currencies) but omits what the tool actually returns and when to invoke it. Without an output schema or explicit purpose, an agent lacks enough context to correctly select and use the tool.

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

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

All five parameters have descriptions, including conditional behavior for paymentSignature and payment-related purposes for creditsWallet and soonHolderWallet. However, the body parameter's description is generic ('JSON POST body for the intel/security route') and does not explain its fields beyond the default value, leaving ambiguity about the request 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 mentions the tool's name and default body with APY sorting, hinting at Meteora yield intelligence, but it never explicitly states what the tool returns or its primary function. The focus is on payment mechanics and the HTTP endpoint rather than a clear verb-object statement of purpose.

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 instead of the many sibling intel_* tools. There is no mention of scenarios, comparisons, or exclusions; the description only covers the endpoint and payment process.

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 does disclose some behavior: it mentions the payment requirement, credit options, and that unpaid calls receive a PAYMENT-REQUIRED challenge. However, it does not state whether the tool is read-only, what side effects occur, or what a successful call returns.

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

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

The description is compact and includes the essential payment and endpoint details, but it is a dense run-on with mixed concerns (pricing, endpoint, default body, unpaid behavior). It could be better organized into separate sentences or sections.

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 a successful response contains or how the momentum intel is presented. Payment edge cases are covered, but the core deliverable of the tool is left undefined.

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?

All five parameters have descriptions, and most are meaningful (agentId, creditsWallet, paymentSignature, soonHolderWallet). The body parameter is only generically described as 'JSON POST body', and its inner fields are not individually documented, so a little clarity is lost.

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 identifies the tool as 'intel-momentum' and gives an endpoint and default body, but never explicitly states what momentum intelligence is retrieved or what the caller should expect. The purpose is implied by the name and default message rather than clearly defined.

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?

There is no guidance on when to use this tool instead of the many sibling intel tools. It explains payment mechanics but not the intended use case or selection criteria relative to alternatives like intel_macro or intel_scalp.

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 payment gate, credits wallet, holder free tier, and payment challenge behavior, but it is vague about success responses, failure modes, and whether the operation is read-only or triggers any side effects.

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

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

The description is a dense run-on of payment terms, endpoint, and default body without clear structure or complete sentences. It is telegraphic and jargon-heavy, making it harder to parse rather than easier.

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 present, and the description never states what a successful response contains. Payment flow details are partial, and the overall behavior—what data is returned for the given symbols and intervals—is missing, leaving important context absent.

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 descriptions for payment-related fields add some context. However, the body parameter is only described as 'JSON POST body' without explaining the symbol/interval semantics or expected response, leaving the meaning of the default body unclear.

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 identifies the tool as 'intel-scalp' and provides an endpoint and default body, but never states what the tool actually returns or what 'scalp' intelligence means. It is not clear how this differs from other intel_* siblings without inferring market-signal 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?

It gives payment-related instructions such as omitting paymentSignature to get a challenge, but does not explain when to choose this tool over siblings like intel_momentum or intel_verdict. No clear use case or selection criteria is provided.

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

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

With no annotations, the description carries the behavioral disclosure burden. It does disclose the paid nature ($0.10), the x402/TCX credit payment paths, and that unpaid calls return a structured payment challenge. However, it says nothing about post-payment behavior, response format, or side effects, leaving a meaningful transparency gap.

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 packs pricing, endpoint, default body, and payment methods into one dense run-on sentence. It is brief but poorly structured; the critical purpose statement is missing and the payment-accept details are buried in a long tail.

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 annotations and no output schema, the description must carry the full burden. It explains payment mechanics and defaults, but omits what the tool computes or returns, how the 'body' parameter is used beyond the default, and what a successful response looks like. An agent cannot confidently invoke this beyond blind forwarding.

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 every parameter is individually documented, so the baseline is 3. The description adds the default body shape and payment-related headers, which slightly enriches context, but most parameter semantics already live in 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 gives the endpoint, pricing, and default payload, but never states what 'intel-trenches' actually does or returns. The name is opaque and no functional verb or resource outcome is provided, so an agent cannot tell whether this provides on-chain trench analysis, sentiment data, or something else.

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 given on when to choose this over the many intel_* siblings. The description explains the payment flow but not the use case, prerequisites, or selection criteria — an agent must guess which intel tool fits a request.

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 behavioral disclosure burden. It does reveal meaningful behavior: the call is paid ($0.10 x402/TCX), the endpoint is a POST, and unpaid calls return live PAYMENT-REQUIRED challenge data. However, it never states what happens after payment, what a successful response contains, or whether the operation has side effects. The provided payment behavior is useful 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 compact and contains several operational details (pricing, endpoint, default body, unpaid behavior) without much waste. However, it is not front-loaded with the tool's purpose; it begins with a redundant repetition of the name and price. It earns some efficiency credit but sacrifices clarity for brevity.

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 external API with multiple payment-related parameters and no output schema, yet the description does not state what the tool returns or how to interpret a successful call. It explains the payment-challenge path but not the actual intel/security results. For an agent to call this confidently, it needs a clear result description and a reason to prefer it over closely named siblings.

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 even with no additional parameter explanation in the description. The description repeats the default body values (chain, limit, maxMcapUsd, meta) but adds no meaning beyond the schema. It does not clarify how limit or maxMcapUsd shape results, nor what meta:'ai' does.

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 opens with the tool name itself ('intel-trenches-screen') and then discusses price, endpoint, and default body, but never states what the tool actually does. It does not say what it screens, analyzes, or returns, and it does not distinguish 'screen' from the sibling intel_trenches tool. This is essentially a tautological label plus API mechanics.

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?

There is no guidance about when to use this tool versus alternatives such as intel_trenches, intel_meteora, or security_scan. The default body hints at Solana low-market-cap queries, but no explicit context, exclusions, or alternative-conditions are provided. The reader must infer use from the tool name and default payload.

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 carry behavioral disclosure. It does describe the payment/challenge flow and headers, but omits side effects, success return data, and whether the operation is read-only.

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 compact but jargon-heavy and confusing; payment details are relevant, but phrasing like 'live PAYMENT-REQUIRED accepts' and mixing currencies/chains without clear structure reduces 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?

No output schema and no annotations; the description fails to explain the core function, success response, or how it fits with sibling tools, leaving the agent under-informed.

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 descriptions cover all 5 parameters at 100%, and the description adds little beyond restating the endpoint and payment options; 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?

Description never states what data or action the tool performs; it only mentions the endpoint, payment methods, and unpaid response behavior. 'intel-tvl' in the name implies TVL intelligence, but no verb or resource outcome is provided.

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

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

No guidance on when to use this tool versus sibling intel_* tools; no criteria, prerequisites, or alternative recommendations are given.

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

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

The description discloses some behavior, such as payment requirements and the option to receive a payment challenge, but it does not describe what happens after a successful call, what data is returned, or what side effects occur beyond payment settlement.

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 and includes necessary payment and endpoint details, though some repetition around payment methods could be tightened. The structure is acceptable for the information conveyed.

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 or description of the response format, making it unclear what the tool returns. The description also lacks context about the 'verdict' semantics, leaving significant gaps for an agent trying to determine expected results.

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?

All parameters are described in the schema, but the descriptions are minimal. For example, 'body' is described only as a JSON POST body for the route without explaining its fields, and 'paymentSignature' references 'x402 settlement' without clarifying the expected format beyond Base64.

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 does not clearly state what action the tool performs or what a 'verdict' means in this context. It mentions the endpoint, default body, and payment but omits the core function and return value, making it hard to distinguish from sibling intel_* 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?

No guidance is provided about when to use this tool versus sibling tools like intel_macro, intel_wallet, or intel_whales. The description focuses on payment mechanics rather than usage context or selection 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?

The description discloses payment gating (unpaid calls return PAYMENT-REQUIRED) and settlement options, but does not explain what happens after payment or any side effects. It also does not clarify whether the tool performs reads, writes, or other operations. The information is fragmented and lacks clarity on the tool's 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 short but poorly structured. It mixes payment details, endpoint URL, and settlement instructions in a way that obscures the tool's purpose. The lack of clear sections or logical flow reduces readability and comprehension.

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 incomplete for a tool with this many parameters and sibling tools. It fails to provide essential context about the tool's function, expected output, or typical use case. The absence of an output schema and the cryptic payment-centric text make it difficult for an agent to know when or how to invoke it correctly.

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

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

Schema coverage is 100% with all five parameters described in the schema (body, agentId, creditsWallet, paymentSignature, soonHolderWallet). The description adds no extra meaning beyond the schema fields; it merely rephrases them. Baseline of 3 is appropriate since the schema already provides full parameter explanations.

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 focuses on payment details (cost, endpoint, settlement) but never states what the tool actually does. It mentions 'intel-wallet' and a POST endpoint, but omits the intended action (e.g., retrieving wallet intelligence). No verb or resource is clearly defined.

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 tools (e.g., intel_airdrop, intel_whales). The description only explains payment mechanics, not usage context or selection 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?

The description discloses payment-related behavior, including the x402 settlement flow, credit alternatives, and the fact that unpaid calls receive a PAYMENT-REQUIRED challenge. However, it does not explain what happens after payment or what data is returned, so behavior is only partially 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 compact but packs pricing, endpoint, default body, and payment alternatives into a single unstructured paragraph. Information is not logically separated, making it harder to parse for an automated agent.

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 involves a payment flow and optional authentication headers, but the description omits the expected output, error scenarios, and how the payment challenge should be handled. Without an output schema or examples, the agent lacks critical context to invoke the tool correctly.

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

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

All parameters have schema descriptions, but several are generic (e.g., body is described only as 'JSON POST body for the intel/security route') and the semantics of 'symbols' are not explained. Payment-related parameters have clearer meaning but the overall parameter purpose remains underspecified.

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 does not explicitly state what the tool does; 'intel-whales' implies whale-related intelligence but the text focuses on pricing, endpoint, and payment mechanics. It lacks a clear verb like 'get' or 'retrieve' and does not describe the actual returned intelligence.

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?

There is no guidance on when to use this tool compared to sibling tools such as intel_macro, intel_wallet, or intel_listing. The description only covers payment details and a default body, leaving the agent to infer the use case from the tool name.

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 payment behavior (x402, credits, free tier) and that unpaid calls return payment challenges, which is useful; however, it omits the core behavior of what the tool does.

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 cluttered with payment specifics but remains brief; structure is acceptable though not elegant.

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

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

Without knowing what intel-wire returns or how it differs from sibling intel tools, the description is incomplete for an agent to decide when to use it.

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?

Each parameter has a description that adds some context (e.g., paymentSignature behavior), but 'body' and 'agentId' remain generic; overall meaning is partially conveyed.

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 focuses on payment and endpoint details but never states what the tool actually does; 'intel-wire' is vague and no verb describes the action.

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

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

No guidance on when to choose this over sibling intel tools; the description only mentions payment mechanics, not use cases.

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 carries the behavioral burden. It discloses the paid nature, the payment methods (x402, TCX credits, SOON holder), and explicitly states that unpaid calls return live PAYMENT-REQUIRED accepts. This is strong transparency about the gating behavior, though it doesn't mention rate limits or response shape for paid calls.

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 information-dense but efficient, front-loading the price and endpoint before diving into payment details. Each sentence adds distinct value (cost, default body, payment flow). It's not overly long given the complexity, though it could be tightened by removing redundant payment 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?

For a paid tool with 5 params, no output schema, and no annotations, the description is reasonably complete on the payment side but leaves a gap: what does a successful (paid) call return? It only describes the unpaid response ('PAYMENT-REQUIRED accepts'). The agent cannot anticipate the actual data structure or error handling for paid calls, which is a notable omission for such a transactional 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 schema already documents all 5 parameters with 100% coverage, so baseline is 3. The description adds meaningful context by explaining the default body, the paymentSignature omission behavior (returning a structured challenge), and the meaning of creditsWallet/soonHolderWallet. This goes beyond the schema's terse descriptions and aids correct invocation.

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 is a paid yield-intel service with a specific endpoint and default body, distinguishing it from generic siblings like intel_macro or intel_meteora by focusing on yields and payment mechanics. It avoids tautology and gives concrete details (price, route). However, it does not explicitly define what 'yields' returns beyond payment-required accepts, leaving some ambiguity.

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 never tells the agent when to choose this tool over the many intel_* siblings. It explains the payment flow but not the use case (e.g., 'use when you need cross-protocol yield data'). No exclusions or alternative routing are provided, so the agent must infer from the name and default body.

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 does disclose payment behavior (unpaid calls return PAYMENT-REQUIRED) and provides a default body, which hints at request behavior. However, it does not disclose what happens on success, whether the operation is read-only, or any side effects, leaving the actual scan behavior 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 a single run-on paragraph mixing pricing, endpoint, default body, and payment notes, making it cluttered and hard to scan. It lacks a clear front-loaded purpose statement and reads more like a billing spec than an API tool 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?

Given there is no output schema, the description should explain what the tool returns or how to interpret the response, but it does not. It also omits any context about the actual scanning logic, prerequisites, or expected outcomes, leaving the tool functionally underspecified.

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 each parameter having a description, and the default body provides a concrete example of nested fields. Nonetheless, the body description is generic ('JSON POST body for the intel/security route') and does not explain each inner field, so it adds only marginal meaning 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 never states what the tool actually does—it only gives an endpoint, payment details, and a default JSON body. The name 'security-deep-scan' implies a function, but no explicit verb or resource outcome is described, making it nearly tautological.

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 given about when to use this tool versus its siblings like security_scan or security_readiness. There is no mention of use cases, prerequisites, or selection 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?

The description discloses payment requirements and that unpaid calls return structured payment challenges, but it does not disclose what happens after payment, whether the tool makes outbound requests to the target, what output formats are returned, or any side effects/limits. With no annotations, these behavioral details are missing.

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 crams pricing, endpoint, default body, and payment behavior into a dense single paragraph. It lacks clear separation between what the tool does, how to invoke it, and what the response means, making it harder to parse for an agent.

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, no description of success responses, error codes, or the payment challenge structure. The tool's place among the security_* sibling tools is also unexplained, leaving important operational context absent.

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?

Top-level payment-related parameters (paymentSignature, creditsWallet, soonHolderWallet, agentId) have clear descriptions, but the critical 'body' object only says it is the JSON POST body and does not explain the semantics of target, allowlist, or authorized. This leaves core parameters underspecified.

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 is mostly an API/payment reference and never explicitly states that the tool scans or inspects security headers for a target. The tool name implies the purpose, but the description itself does not clearly define the action compared with sibling security 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?

No guidance is provided about when to use this tool versus security_scan, security_deep_scan, or security_readiness. The description focuses on pricing, endpoint, and payment mechanics rather than usage context or selection 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, the description must disclose all behavioral traits. It mentions payment-related behavior (unpaid calls return PAYMENT-REQUIRED accepts) but does not describe what a successful call does, what it returns, or any side effects. The core behavior of the tool is absent.

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

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

The description is concise but poorly structured. It leads with cost and endpoint rather than the tool's purpose, burying the only functional hint (the default body) in the middle. Not front-loaded, and the payment details dominate.

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 5 parameters, no output schema, and no annotations, the description is severely incomplete. It lacks a statement of what the tool does, when to use it, and what it returns. An agent cannot correctly invoke it without guessing the purpose and outcome.

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 schema already documents each parameter. The description adds the default body example and payment context, but these do not add meaningful semantics beyond the schema. Baseline 3 is appropriate.

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

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

The description provides an endpoint and default body but never explicitly states what the tool does. It mentions 'security-readiness' and 'intel/security route' in the schema, but the core purpose (e.g., evaluating security readiness of a target) is only implied. It does not clearly differentiate from sibling security tools like security_scan or security_headers.

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 given on when to use this tool versus alternatives. There is no mention of scenarios, prerequisites, or exclusions. An agent has no way to decide if this tool is appropriate for a given task.

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 payment requirements, the PAYMENT-REQUIRED response for unpaid calls, and credit/free-tier options. However, it does not describe side effects, authorization implications, or what happens after a successful scan, and there are no annotations to cover these.

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 compact and contains relevant payment and endpoint details, but it is structured as a dense run-on block rather than a clear purpose-first description. The payment details dominate while the core action and output are not 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?

The description lacks information about the expected response, success criteria, or output format, and there is no output schema to fill that gap. It also omits when to choose this scan over related security tools, leaving the context incomplete for an agent.

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

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

All top-level parameters have descriptions, and paymentSignature is explained well. However, the body parameter is only described as the JSON POST body and its nested fields (target, allowlist, authorized) are not semantically explained beyond the default values.

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

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

The description names the tool as security-scan and includes a default body with target and allowlist, implying a security scanning action, but it never explicitly states what the tool does or what kind of scan it performs. The purpose is inferable but not clearly declared.

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 sibling tools like security_deep_scan, security_headers, or security_readiness. It focuses on payment mechanics rather than selection criteria.

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