Concierge Intel

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

With no annotations, the description must fully convey behavior. It states 'Free' (non-destructive) and 'list' (read-only), and lists included data. It lacks mention of rate limits or data freshness but is sufficient for a simple read operation.

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

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

Two short sentences front-load the key information: free, list, and what is listed. Every word contributes; 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?

Despite no output schema, the description explains what the tool returns (prices, paths, curl hints) and when to use it. For a simple listing with zero required params, this is complete.

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

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

Input schema coverage is 100% with a clear description for the prefix parameter. The description adds no additional meaning beyond the schema, so baseline of 3 applies.

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

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

The description specifies 'list Concierge MCP paid tools' identifying the exact verb and resource. It is clearly distinct from sibling tools like concierge_prepare_payment and intel_* tools which are actual tools rather than a catalog.

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

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

The phrase 'Call before paying' gives an explicit usage context. It does not directly compare to alternatives, but the sibling list implies this tool is for browsing before payment.

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

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

No annotations provided; description claims 'Free' but does not disclose any behavioral traits such as idempotency, side effects, or whether it requires prior authentication. Lack of detail on what 'live x402 challenge' entails.

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

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

Single sentence, no fluff. Efficiently communicates core function.

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

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

Adequate for a simple tool with one parameter and no output schema. However, missing details about response format, error handling, and prerequisite steps for the payment flow.

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

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

Schema has 100% coverage with a description for 'kind'. Description adds 'paid tool kind' context but does not significantly enhance the schema's documentation.

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

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

Description clearly states it returns a payment challenge for a paid tool, distinguishing the payment preparation step from the paid tools listed as siblings. The term 'x402 PAYMENT-REQUIRED challenge' is specific but jargon-heavy.

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

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

Implies usage before calling a paid tool ('so a wallet / pay.sh can settle before tools/call'), but lacks explicit when-not to use or alternatives. No guidance on prerequisites like authentication.

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

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

No annotations provided, so description must cover behavioral traits. It discloses payment requirements, endpoint, and default body, and mentions that unpaid calls return a payment challenge. However, it does not describe what the pipeline does internally, return format, or side effects beyond 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?

Description is relatively concise, front-loading the tool name and cost before technical details. It packs endpoint, default body, and payment info into a single paragraph. Could be slightly more structured but effective.

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 omits what the tool returns or how the pipeline outcome looks. Sibling tools suggest it produces some intel result, but this is not clarified. The description feels incomplete for a tool requiring payment and orchestration.

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 parameters are well-described in the schema. The description adds minimal extra meaning beyond showing default body example and payment context. Baseline of 3 is appropriate as the schema carries the burden.

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

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

The description states the tool is an 'intel-a2a-pipeline' with a specific endpoint and default body, indicating it orchestrates A2A intel tasks. However, the purpose is somewhat obscured by heavy payment mechanics. It clearly distinguishes itself from siblings by mentioning 'A2A orchestration' but could be more explicit.

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 tools like intel_desk_brief or intel_scalp. The description focuses on payment details rather than use cases or prerequisites. An agent has no basis to choose this over 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?

With no annotations, the description must disclose behavioral traits. It reveals payment requirements and default body parameters, but fails to explain behavioral aspects like rate limits, resource consumption, or side effects. The note on 'Unpaid calls return live PAYMENT-REQUIRED accepts' adds some insight but is insufficient for full transparency.

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

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

The description is short and includes key details like payment and default body, but it is somewhat fragmented and could be better structured. The first sentence mixes the tool name, cost, and endpoint, making it less readable. It is concise but not optimally organized.

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

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

Given 5 parameters, nested objects, no output schema, and many sibling tools, the description is incomplete. It does not explain what the tool returns, how to interpret results, or how to handle payment flows. The focus on payment overshadows the tool's core functionality, leaving significant gaps 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?

Schema coverage is 100%, so baseline is 3. The description repeats the default body values but does not add significant new meaning beyond the schema descriptions. It mentions that 'body' is for the 'intel/security route' and hints at payment parameters, but this is minimal added value.

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

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

The description states it is for 'intel-airdrop' and includes a default body for 'Solana ecosystem airdrop farming', which vaguely indicates its purpose. However, it does not clearly specify what the tool returns or how it differs from other intel tools beyond the name. The inclusion of a POST endpoint and payment details adds context but lacks a precise verb+resource description.

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

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

No explicit guidance on when to use this tool versus alternatives. It mentions payment requirements but does not provide context on when to choose this over sibling tools like 'intel_verdict' or 'intel_wallet'. The description implies it is for airdrop-related intelligence but offers no usage scenario or conditions.

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

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

Without annotations, the description must fully disclose behavior. It covers payment flow (unpaid calls return PAYMENT-REQUIRED) but omits what a successful call returns, side effects, or whether it requires prior setup.

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 key details (price, endpoint, default body, payment behavior) front-loaded. However, it mixes payment mechanics with functional description, which could be more logically 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?

Given 5 parameters, nested objects, no output schema, and no annotations, the description is incomplete. It lacks success response format, error handling, and configuration guidance beyond the default body.

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 includes descriptions for all parameters. The description adds the default body example, which provides context beyond the schema's default values, but does not explain parameter relationships.

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 'morning desk brief' and the default body, implying it fetches a daily brief. However, it does not explicitly state the tool's core function (e.g., 'retrieve a morning intelligence summary'), and among many intel_* siblings, the purpose is not clearly 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?

No guidance on when to use this tool versus alternatives like intel_macro or intel_whales. It provides technical details (endpoint, payment) but no contextual usage cues.

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 tool requires payment ($0.10 USDC x402 or TCX credits) and that unpaid calls return a PAYMENT-REQUIRED response. This is valuable behavioral context given the absence of annotations. However, it does not mention rate limits, side effects, or authentication beyond payment headers, leaving gaps in understanding.

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

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

The description is a single dense sentence covering endpoint, cost, default body, and payment behavior. It is efficient but could be better structured (e.g., separate lines for key aspects). No extraneous text, but it packs a lot into one sentence.

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, low annotation coverage, and 5 parameters, the description should clarify the response format and error handling. It only explains payment and endpoint, leaving the agent guessing about return values, pagination, or failure modes. For a paid tool, this is a significant gap.

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

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

Input schema covers all 5 parameters with descriptions, achieving 100% coverage. The description adds value by showing default body ('message' and 'limit') and hints at payment-related parameters (creditsWallet, paymentSignature, soonHolderWallet). Beyond defaults, it does not explain parameter constraints or interactions, so it only marginally improves on 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 states the tool is for 'intel-listing' and provides a default body with 'Potential exchange listings', indicating it retrieves a list of potential exchange listings. The verb is implicit via POST, and the resource is clear from the URL. However, it does not differentiate this tool from sibling intel tools (e.g., intel_verdict, intel_whales) which could have overlapping purposes.

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 the many sibling intel tools. It mentions payment requirements but does not specify use cases or alternatives. An agent would have no context to decide between intel_listing and, say, intel_macro or intel_wallet.

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

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

With no annotations, the description carries the burden. It discloses the payment-gated nature, default body, and the behavior of unpaid calls returning PAYMENT-REQUIRED. However, it does not describe side effects, idempotency, or successful response 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 extremely concise (27 words) and front-loaded with cost and endpoint. Every sentence provides distinct info (name, cost, endpoint, default, behavior). No waste.

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

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

Despite having 5 parameters and no output schema, the description only explains payment-related behavior. It omits what a successful response contains, what the tool actually does (beyond being a POST endpoint), and any return structure. For a payment-gated tool, this is insufficient.

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

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

Schema coverage is 100%, baseline 3. The description adds value by explaining the default body, the effect of omitting paymentSignature (structured challenge), and mapping parameters to headers (creditsWallet, soonHolderWallet). This goes beyond 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 mentions 'intel-macro' and the endpoint, but lacks a specific verb and resource. It does not clearly state what the tool does (e.g., retrieve, analyze), making its purpose vague compared to siblings like intel_scalp or intel_whales which imply specific functions.

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

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

No guidance is provided on when to use this tool versus alternatives. The description focuses on payment mechanics but offers no contextual or exclusivity hints relative to sibling tools.

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

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

Given no annotations, the description discloses key behavioral traits: pricing ($0.10 USDC x402 or TCX credits), endpoint URL, default body, and that unpaid calls return PAYMENT-REQUIRED. This helps the agent understand payment requirements and expected 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 very short and packs technical details (pricing, endpoint, default body, payment behavior) into two sentences. However, it lacks a clear purpose statement, which slightly reduces effectiveness.

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, and the description does not specify what the tool returns beyond payment status. With 5 parameters and a paid API, the description is incomplete about core functionality, leaving the agent uncertain about the tool's actual output.

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

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

Schema coverage is 100% with parameter descriptions. The description adds no additional meaning to parameters beyond what is in the schema (e.g., default body is already in schema). 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 does not explicitly state what the tool does; it focuses on payment mechanics and endpoint details instead of the tool's function (e.g., retrieving Meteora data). The phrase 'intel-meteora' implies intelligence information, but the purpose remains 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 over its many siblings (e.g., intel_yields, intel_tvl). The description does not mention context, prerequisites, 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?

Discloses payment requirement and that unpaid calls return PAYMENT-REQUIRED. However, no other behavioral traits (e.g., data freshness, rate limits) are 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?

Description is a single run-on sentence mixing pricing, endpoint, default body, and a note about payment. Poorly structured and 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?

No output schema and description does not explain return values or how to interpret the payment flow. Incomplete for a tool requiring payment and having multiple parameters.

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 descriptions cover parameters adequately. The description adds default body but does not provide additional semantic value beyond what is 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 focuses on HTTP endpoint and cost, but fails to state what the tool does. 'intel-momentum' is vague and not differentiated from many intel_* siblings.

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

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

No guidance on when to use this tool versus alternatives like intel_listing or intel_scalp. The description provides no usage context.

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

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

With no annotations, the description bears full responsibility. It discloses that the tool has a cost ($0.10 USDC) and that unpaid calls result in a PAYMENT-REQUIRED response, but it does not explain what the tool does when paid. The behavior after successful payment is opaque. This is insufficient for a tool with payment constraints.

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

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

The description is a single, run-on sentence with mixed technical details (price, endpoint, default body, payment behavior). It lacks clear structure and is not easy to parse quickly. Each element could be separated for clarity.

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

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

The tool has 5 parameters, a payment model, and no output schema. The description omits what the tool returns or how it integrates with other tools. It fails to provide a complete picture for an agent to correctly invoke the tool, especially regarding the output behavior.

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 coverage is 100%, so the schema already describes parameters. The description adds the default body structure and clarifies payment-related parameters (creditsWallet, paymentSignature, soonHolderWallet). While helpful, it does not significantly expand on the schema descriptions. A 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 does not clearly state what the tool does. It mentions the endpoint, default body, and payment model but lacks a specific verb and resource. The name 'intel-scalp' suggests some intelligence or scalp-related data, but the purpose remains vague. Sibling tools have clearer names like 'intel_macro' or 'intel_tvl'.

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 the many sibling tools (e.g., intel_macro, intel_tvl). It only describes the call format and payment requirements. No explicit when-to-use or when-not-to-use information is given.

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

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

The description discloses that unpaid calls return a payment challenge, which is a behavioral trait. However, it fails to describe the normal behavior of a paid call (i.e., what data is returned). With no annotations, the description does not fully characterize tool 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 concise, containing only necessary technical details, but it is poorly structured. It mixes purpose, endpoint, default body, and behavior in a single run-on sentence, lacking clear segmentation or front-loading of purpose.

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

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

Given 5 parameters, nested objects, and no output schema, the description is incomplete. It omits the tool's primary function, expected return format, and when it should be invoked, leaving significant gaps for an AI agent.

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

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

Schema coverage is 100%, so parameter descriptions exist. The tool description adds context about the payment flow (e.g., default body, payment acceptance) but does not significantly enhance parameter meaning beyond the schema. Baseline 3 applies.

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

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

The description does not clearly state what data the tool returns. It mentions the endpoint and payment details but omits the tool's core function (e.g., retrieving TVL data). The name 'intel_tvl' hints at total value locked, but no explicit verb or resource is given.

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

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

No guidance on when to use this tool vs. the many siblings (e.g., intel_macro, intel_wallet). The description only addresses payment mechanics, not use cases 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?

No annotations provided. The description partially discloses that unpaid calls return a PAYMENT-REQUIRED response, but lacks details on rate limits, destructive actions, or other behaviors.

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 cryptic and lacks proper sentences. It conveys necessary info but is not well-structured for easy 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?

No output schema exists, yet the description doesn't explain return values beyond mentioning payment challenges. With 5 parameters and nested objects, the description is incomplete.

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

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

Schema coverage is 100%, so the schema already documents parameters. The description adds payment context (default body, signature flow) but doesn't significantly enhance understanding beyond schema.

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

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

The description focuses on cost and endpoint rather than a clear verb+resource. It's unclear what 'intel_verdict' actually does; it seems to be a paid API call but not differentiated from siblings like intel_macro or intel_whales.

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

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

No guidance on when to use this tool vs alternatives. The description only mentions payment methods, not context or prerequisites.

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

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

With no annotations, the description must disclose behavioral traits. It mentions payment requirements and the default POST body, but does not explain what happens upon successful payment (e.g., what data is returned), how the tool handles errors, or what 'live PAYMENT-REQUIRED accepts' means. The behavior is 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 short and to the point, with no redundant information. It conveys the endpoint, default body, and a key behavior (payment required) in a few lines.

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

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

Given 5 parameters, nested objects, no output schema, and no annotations, the description is insufficient. It does not explain the tool's purpose, return values, or how parameters interact. The agent lacks context to use the tool effectively.

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

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

Schema description coverage is 100%, so the schema already documents all parameters. The description adds the endpoint URL and a concrete default body example, which provides context. However, it does not clarify the meaning of params like agentId, creditsWallet, etc., 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 focuses on the payment mechanism ($0.10 USDC x402, POST endpoint, default body) rather than stating what the tool does. It does not indicate that 'intel-wallet' provides intelligence about a wallet. The mention 'Unpaid calls return live PAYMENT-REQUIRED accepts' is confusing and does not clarify the tool's core function. Among many intel_* siblings, this lacks differentiation.

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 the numerous sibling intel tools (e.g., intel_whales, intel_airdrop). The description does not specify use cases, prerequisites, 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?

Discloses payment requirement via x402 or TCX credits and that unpaid calls return PAYMENT-REQUIRED. However, lacks details on success behavior, data format, idempotency, or rate limits. With no annotations, description carries full burden but is 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?

Description is short but lacks clear sentence structure. It mixes technical details (endpoint, payment) with default body info. Could be more concise and front-loaded with purpose.

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

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

No output schema, so return values and error handling are not explained. Payment mechanism is described but unclear what constitutes a successful call. Incomplete for a paid API tool with complex parameters.

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. Description mentions default body with symbols but adds little beyond schema descriptions. No extra parameter semantics provided.

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 mentions 'intel-whales' and provides endpoint and default body, implying data retrieval for symbols, but does not explicitly state that it returns whale intelligence or analysis. Purpose is implied but not clear.

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

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

No guidance on when to use this tool versus the many sibling intel tools. Does not differentiate use cases or provide context for selection.

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

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

With no annotations, the description carries the transparency burden. It discloses the payment requirement (unpaid calls return PAYMENT-REQUIRED) and mentions available payment options (USDC x402, TCX credits). However, it does not reveal whether the tool is read-only or has side effects, nor what the response contains after successful 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 short (3 sentences) and packs multiple details (cost, endpoint, default body, payment behavior). It is efficient but lacks clear separation of concerns (purpose vs. mechanics).

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

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

Given 5 parameters, no output schema, and 18 sibling tools, the description is incomplete. It ignores return values, how to handle payment challenges, and differentiation from other intel tools. The agent would need to infer too much.

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

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

Schema description coverage is 100%, so the baseline is 3. The description adds no extra semantic value beyond the schema; it only repeats the default body. All parameters are already well-documented 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 mentions 'intel-wire' and provides the endpoint URL, but does not explicitly state what the tool does or what kind of intel it returns. It focuses on payment mechanics rather than the core function, leaving the purpose somewhat implied.

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 versus its many intel siblings. The description only mentions that unpaid calls return payment required, but does not help an agent decide when to invoke it.

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

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

No annotations are provided, so the description must disclose all behavioral traits. It mentions payment requirements and that unpaid calls return a 'PAYMENT-REQUIRED' accept, but fails to describe what happens after payment, the return format, or any side effects. This is insufficient for a complex, payment-gated tool.

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

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

The description is brief (29 words plus a code snippet) and front-loads the cost and endpoint. Every sentence adds unique information, but the structure could be improved by separating payment details from functionality.

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

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

Given the tool has 5 parameters, no output schema, and no annotations, the description is incomplete. It omits return value details, prerequisites (e.g., wallet), and the complete payment flow beyond the initial response. An agent would lack essential context for correct invocation.

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

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

The input schema covers all 5 parameters with descriptions (100% coverage). The description adds only the default body value, which is already in the schema default. No further semantic enrichment is provided, 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 mentions 'intel-yields' and provides a default body specifying chain and project, implying it retrieves yield data. However, it lacks a clear verb (e.g., 'fetch' or 'get') and does not explicitly state what the tool does, leaving ambiguity. Sibling tools like 'intel_meteora' suggest possible overlap, but no differentiation is given.

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

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

No guidance on when to use this tool over alternatives like 'intel_meteora' or 'intel_macro'. The description focuses on payment mechanics rather than use cases, leaving the agent without context for appropriate invocation.

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 endpoint, payment requirements, and that unpaid calls return a payment challenge. However, it does not describe the tool's output on success (e.g., what security headers are returned), which is a significant gap for a security analysis tool.

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

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

The description is a single block of technical details including full URL, default JSON, and payment options. It front-loads the name and price but could be more structured (e.g., separating usage from payment). It is not overly verbose but could be clearer.

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

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

Given the tool has 5 parameters, nested objects, no output schema, and many siblings, the description is incomplete. It does not explain the return value on success, nor does it differentiate from similar tools. The payment behavior is well-covered, but the core functionality is 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 description coverage is 100%, so baseline is 3. The description adds context about the default body and payment flow (creditWallet, soonHolderWallet), but mostly repeats schema descriptions. It explains when to omit paymentSignature to receive a challenge, which adds some value 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 implies the tool checks security headers via a POST request to a specific endpoint with a default target and allowlist. However, it never explicitly states 'check security headers' or 'analyze HTTP security headers', relying on the tool name and endpoint path. It does not distinguish from sibling tools security_readiness and security_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?

No guidance is provided on when to use this tool versus alternatives like security_scan or security_readiness. The description focuses on payment mechanics (x402, credits) but gives no context for tool selection or exclusions.

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

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

The description mentions that unpaid calls return a PAYMENT-REQUIRED response, but it does not disclose what happens on a successful paid call, the nature of the result, rate limits, or any side effects. With no annotations, the description carries the full burden and falls short.

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 concise, fitting in three short segments. It avoids fluff but mixes payment, URL, and default body without clear separation. Could be slightly more structured, but overall efficient.

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 5 parameters, no output schema, and no annotations. The description omits critical information such as the expected output of a successful call, error handling beyond payment, and the relationship to sibling tools. It is insufficient for an agent to fully understand the tool's behavior.

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 descriptive parameter names and brief descriptions. The tool description adds value by showing the default body structure and specifying the URL, which clarifies the purpose of the 'body' parameter beyond the schema. However, it does not explain the optional parameters like agentId or creditsWallet in detail.

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 a security-readiness endpoint with a specific URL, default body, and payment model. It clearly names the resource and action, distinguishing it from sibling tools like security_headers or security_scan, but does not elaborate on the output or success criteria.

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

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

No guidance is provided on when to use this tool versus its siblings. The description focuses on payment and invocation details but does not explain the context or alternatives for choosing security_readiness over other security tools.

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

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

With no annotations, the description fails to disclose key behavioral traits such as whether the scan is destructive, what happens on success/failure, or rate limits; only mentions payment 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?

Description is a single paragraph with multiple pieces of information (pricing, URL, default body, payment note) but lacks a clear front-loaded purpose statement; not overly long but could be better 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?

Given the complexity (5 parameters, nested object, no output schema, payment integration), the description is incomplete: it does not explain the scan result, error handling, or how the payment challenge works in detail.

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 parameters are documented; description adds a default body and explains payment flow, but does not clarify the role of parameters like 'allowlist' or 'authorized' in the scan context.

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

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

Description does not explicitly state what the tool does; it uses the tool name followed by pricing and URL, leaving the purpose to be inferred from the default body with 'target' and 'allowlist' fields.

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 tools like security_headers or security_readiness; no mention of alternatives or prerequisites.

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