Concierge Intel

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

No annotations are provided, so the description must carry the full burden. It does not explicitly state that the operation is read-only or non-destructive, nor does it disclose any authentication or rate-limiting behavior. The word 'Free' hints at no cost but not safety.

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

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

The description is a single sentence that front-loads the key benefit ('Free') and concisely lists what the tool returns. Every phrase earns its place with no wasted words.

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

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

For a simple listing tool with no output schema, the description adequately describes the output contents (prices, paths, curl hints). The single optional parameter is fully documented in the schema, and the low complexity means no further context is needed.

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

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

The input schema has 100% description coverage for the single optional parameter 'prefix'. The tool description adds no additional meaning beyond what the schema already provides, so 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 lists Concierge MCP paid tools with prices, paths, and curl hints. It distinguishes from siblings like concierge_prepare_payment and the many intel/security tools by focusing on the catalog aspect.

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' implicitly tells the agent to use this tool before payment. While it doesn't explicitly mention alternatives, the sibling names suggest this is a discovery tool, giving clear context.

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

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

With no annotations, the description carries full burden for behavioral traits. It mentions it's 'free' and returns a challenge, but it doesn't disclose error behavior for invalid kinds, idempotency, rate limits, or authorization requirements. The term 'base64 accepts' is vague.

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

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

The description is a single sentence, concise and front-loaded. However, it uses jargon ('x402', 'base64 accepts') that may reduce clarity. Could be slightly more accessible while remaining brief.

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

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

For a simple tool with one parameter and no output schema, the description covers the basic action and return value. Missing details: error handling for invalid 'kind', exact format of the challenge, and whether the challenge is one-time only. Adequate but not 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?

Schema coverage is 100% with a clear parameter description including examples. The main description adds 'for a paid tool kind', which implies a constraint, but doesn't provide additional semantic detail beyond the schema. Baseline 3 is appropriate.

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

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

The description clearly states the tool returns a live x402 PAYMENT-REQUIRED challenge for a paid tool kind, which is a specific verb+resource. It distinguishes itself from sibling tools like concierge_catalog and various intel/security tools by being payment-specific.

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

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

The description indicates usage before calling a paid tool ('so a wallet / pay.sh can settle before tools/call'), providing clear context. However, it does not explicitly state when not to use or mention alternatives, though no obvious alternatives exist among siblings.

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 is transparent about payment requirements: cost, accepted currencies, and behavior of unpaid calls (returning PAYMENT_REQUIRED). However, it lacks disclosure of the tool's outcome after payment (e.g., whether it mutates state or returns data), and no annotations are provided to fill this 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 is a single dense paragraph that covers endpoint, default body, and payment details efficiently. It's concise without wasting words, though it could be better structured with bullet points 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?

Missing critical details: no output schema, no explanation of return value after payment, no guidance on which payment method to use or how to handle PAYMENT_REQUIRED responses. For a paid API with multiple payment options and a nested object parameter, 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% with parameter descriptions. The description mentions the default body, which matches the schema's default value, but adds no new semantic meaning beyond what the schema provides. Baseline of 3 is appropriate.

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

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

The description states the tool is a 'pipeline' for 'Solana desk A2A orchestration' but doesn't clearly define what it accomplishes. It focuses on payment and endpoint details rather than the core function, making it vague compared to sibling tools like intel_macro or intel_wallet which have clearer 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?

No guidance on when to use this tool versus other intel_* tools. It only mentions the default body and payment requirement, but doesn't explain scenarios where this pipeline is appropriate or when to modify parameters.

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 payment-required behavior and supported currencies but fails to explain key behavioral aspects: what happens after payment (e.g., returned data format or action), rate limits, or any side effects. Since no annotations exist, the description carries full responsibility, and it 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 brief and packs essential details (endpoint, payment, default body) into one paragraph. It could be improved by separating conceptual elements (purpose vs. payment), but it avoids unnecessary verbosity.

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

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

With no output schema, 5 parameters including a nested object, and a payment-gated workflow, the description fails to explain what the tool returns or how to complete the full interaction. It omits crucial context like error handling, pagination, or data structure, making it incomplete for an agent to reliably invoke.

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 5 parameters have descriptions in the input schema (100% coverage), so the baseline requirement is met. The description adds value by showing the exact default body and explaining the payment signature's role. However, it does not clarify the semantics of nested objects beyond what the schema already provides.

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

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

The description clearly states it's an 'intel-airdrop' tool with specific payment methods and a POST endpoint. It includes the default request body, making the purpose identifiable. However, it lacks a concise statement of what airdrop intelligence is actually delivered (e.g., data retrieval or submission), requiring inference.

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 (e.g., intel_listing, intel_whales). The description focuses on the payment flow rather than usage context, leaving an agent without decision support for tool 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?

The description discloses the payment flow, endpoint, and default payload, but lacks details on what the successful response contains (no output schema). Since no annotations are provided, the description shoulders the burden, yet it omits behavioral traits like rate limits or error handling 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?

The description is a single, dense paragraph that packs essential info (cost, endpoint, default body, payment methods) without unnecessary words. It could benefit from slight restructuring for readability but remains 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 description adequately covers input and payment mechanism, but does not describe the response format or behavior after successful payment. Given the complexity of a paid tool with 5 parameters and nested objects, omitting return value details makes it slightly 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%, and the description adds meaning by explaining the default body structure and clarifying the payment-related parameters (creditsWallet, paymentSignature, soonHolderWallet). This helps an agent understand how to settle payments beyond the schema.

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

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

The description clearly states the tool provides a morning desk brief via POST, specifying the endpoint and default body. It distinguishes from many sibling intel tools (airdrops, macro, etc.) by its specific focus on a daily briefing.

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

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

The description explains the payment requirement and that unpaid calls return a payment challenge, implying usage after payment. However, it does not explicitly state when to use this tool versus other intel tools or provide alternative names.

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 fully disclose behavior. It explains the payment requirement ($0.10), the payment methods, and that unpaid calls return a PAYMENT-REQUIRED challenge. However, it does not describe what happens after payment, the response format, or any rate limits or destructive 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 concise but packs many details (pricing, URL, default body, payment details) into a single sentence. It lacks clear structure or front-loading of the core purpose. The payment details dominate, making the tool's primary function harder to grasp 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?

No output schema exists, and the description fails to describe the response for paid calls—what data is returned (e.g., exchange names, dates, etc.). For a paid tool, this omission is significant. The description is incomplete for an agent to reliably invoke and interpret 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?

The schema covers all 5 parameters with descriptions. The description adds value by explaining the default body, the role of paymentSignature (omitting triggers a challenge), and the purpose of creditsWallet and soonHolderWallet. This extra context helps an agent understand the payment flow, going beyond bare 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 indicates the tool provides 'Potential exchange listings' intel via a POST request, but the purpose is somewhat obscured by prominent payment details and the URL. The verb 'intel-listing' and default body message clearly imply retrieval of listing intelligence, distinguishing it from siblings like intel_airdrop or intel_macro, though not explicitly.

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

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

No guidance on when to use this tool versus sibling intel tools. The description mentions payment requirements but does not explain the context or prerequisites for use. An agent would not know which scenario warrants intel_listing over others.

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 mentions payment handling and x402 protocol but does not explain what the tool does, what it returns, or any side effects. Critical behavioral aspects are omitted.

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. It is not front-loaded with the tool's purpose, instead mixing payment details and endpoint. Could be more 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 tool has 5 parameters, no output schema, and no annotations, the description is severely incomplete. It does not explain return values, use cases, or how the tool fits with its many 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 coverage is 100%, so each parameter is already described in the schema. The description does not add extra meaning beyond mentioning the default body. 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 mentions 'intel-macro' but does not specify what macro intelligence it provides. It focuses on payment details and the endpoint, leaving the tool's purpose vague. Sibling tools like 'intel_wallet' or 'intel_whales' have clearer names, but this one does not differentiate.

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 other intel tools. The description implies a payment model but does not clarify scenarios where this tool is appropriate.

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

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

Describes the HTTP method, default body, payment process, and behavior on unpaid calls (returns structured payment challenge). However, it does not mention rate limits, authentication beyond payment, or whether the tool is destructive. With no annotations, the description carries the burden and is partially adequate.

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

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

The description is a single dense sentence containing endpoint, default body, and payment info. It is moderately concise but lacks clear structure (e.g., bullet points or sections) and mixes technical details with payment options, making it less readable.

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

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

Lacks explanation of return values (no output schema), prerequisites (e.g., wallet for credits), and what the data represents. The description focuses on payment mechanics but omits what the user gets in response, which is critical for tool selection and invocation.

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

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

Schema description coverage is 100%, so the schema already explains each parameter. The description adds context about the endpoint and credits usage but does not significantly enhance parameter meaning beyond defaults. 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 states it's a POST request to fetch intel data from meteora with default sorting by APY. It clearly identifies the endpoint and payment requirements. However, it does not explicitly differentiate from sibling tools like intel_yields or intel_tvl, which could also fetch yield or TVL data.

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 focuses on payment methods and API details but does not provide decision criteria for choosing between intel_meteora and other intel tools.

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

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

The description explains payment requirements and supported tokens/chains, which is important behavioral context. However, it does not disclose what the tool does with the input (e.g., whether it mutates state), response format, or any side effects. Without annotations, more detail on the operation's nature would be helpful.

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 mixing pricing, endpoint, default body, and payment methods. It lacks structure and is hard to parse. Could be broken into clear sections for purpose, parameters, and payment.

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 what the tool returns (output). With no output schema, the agent needs to know what to expect from a successful call. Also lacks details on error handling or rate limits, leaving gaps for a 5-parameter tool.

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

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

With 100% schema coverage, the description adds meaning to the body parameter by providing a default and context. It also clarifies the purpose of paymentSignature, creditsWallet, and soonHolderWallet, supplementing the schema descriptions.

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

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

The description mentions 'intel-momentum' and provides a URL and default body, implying it fetches momentum data, but never explicitly states the function. The focus on pricing and payment obscures the core 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 on when to use this tool versus sibling intel tools. The description focuses on payment mechanisms, not on use cases or conditions that warrant choosing this tool.

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

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

Since no annotations are provided, the description carries the full burden. It discloses that unpaid calls return PAYMENT-REQUIRED accepts and explains payment methods. However, it does not describe what the tool returns upon payment, whether it is read-only or destructive, or 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 single dense sentence packed with technical details. It could be more concise and front-loaded with the tool's purpose, but it is not overly long.

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 payment mechanics and default body, but lacks return value information (no output schema). It also does not situate the tool among its many siblings. For a paid API with default parameters, more context is needed.

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

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

Schema description coverage is 100%, and the parameter descriptions are clear. The description adds some context about default body and payment flows, but does not significantly enhance understanding 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 fetches scalp/intel data for given symbols and intervals, but it does not explicitly state the core purpose. It focuses more on payment and endpoint details. Among siblings like intel_macro or intel_whales, the differentiation is unclear.

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 intel_* tools. The description gives no context about the problem it solves or when it is appropriate 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?

Without annotations, the description must disclose all behaviors. It mentions payment requirements and default body, but fails to detail response format, side effects, rate limits, or what happens after successful payment. Significant gaps.

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

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

The description is dense but front-loaded with the essential purpose and payment. However, the multiple symbols and parentheses make it slightly cluttered. Generally 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?

Given no output schema and many sibling intel tools, the description should explain what TVL data is returned. It does not, leaving the tool's output vague. The payment flow is detailed but the core function is under-specified.

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, the purpose of paymentSignature (omit to get a challenge), and the credit/wallet parameters. This goes beyond the schema comments.

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 the tool calls an API endpoint for TVL intelligence with payment details. However, it does not clarify what TVL data is returned, leaving some ambiguity. Distinguishes from siblings by the specific endpoint and payment mechanism.

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

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

The description implies usage for paid TVL queries but provides no explicit guidance on when to choose this tool over sibling intel tools. No alternatives or exclusions mentioned.

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

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

The description discloses payment behavior (unpaid calls return PAYMENT-REQUIRED) and default body, but lacks broader behavioral context (e.g., rate limits, authentication beyond payment, or what happens after a successful paid call). No annotations are present to supplement.

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 paragraph that packs pricing, URL, default body, and payment instructions. While not overly long, it is dense and somewhat disorganized, 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 lacks information about the tool's output or return values, which is critical since no output schema exists. The purpose is unclear, and the payment-centric focus leaves the user uncertain about what the tool actually provides after payment.

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 already documented. The description adds minor value by providing an example default body and clarifying that omitting paymentSignature returns a payment challenge. However, it largely repeats schema information.

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-verdict' and an 'intel/security route' but does not clearly state what the tool does. It focuses on pricing, payment methods, and default body structure, leaving the core purpose vague. The name suggests a verdict or analysis, but that's implied rather than 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 is provided on when to use this tool versus its many siblings (e.g., intel_whales, security_deep_scan). The description discusses payment flow but 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?

Without annotations, the description carries the full burden. It discloses that unpaid calls return PAYMENT-REQUIRED accepts, a key behavior. However, it lacks details on expected output, error states, or idempotency, leaving gaps.

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

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

The description is compact but mixes technical endpoint details, pricing, default body, and behavior in a single block. It could be better structured with separate sentences for purpose, usage, and behavior.

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 what the tool returns, how to interpret responses, or handle errors. An agent would lack sufficient context to use the tool correctly in a workflow.

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 general payment context (x402, TCX credits) but does not elaborate on individual parameters beyond what the schema already states. No redundant repetition, but also no significant 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 focuses on payment details (x402, credits, endpoint) but does not clearly state what the tool does. It mentions 'intel/security route' but the core function is ambiguous, making it hard to distinguish from siblings like intel_scalp or intel_macro.

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 intel_* siblings. The description does not mention prerequisites, context, or alternatives, leaving the agent without decision 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?

Given no annotations, the description bears full burden. It reveals payment requirements (x402, credits) but does not describe what the tool actually does (e.g., returns whale data, types of analysis). Behavioral traits like latency, required auth, or data scope 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 is a run-on sentence mixing unrelated details (cost, URL, body, payment methods). It lacks paragraphing or bullet points, making it hard to parse quickly. Not concise despite short 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?

No output schema and 5 parameters with nested objects. The description fails to explain return values, error states, or the nature of the intelligence provided. Critical context like what 'whales' means or how to interpret results is 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 coverage is 100% so baseline is 3. The description adds value for some parameters (default body, paymentSignature) but does not explain how they influence the tool's behavior or output. No meaningful semantic enrichment overall.

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 a mix of pricing, URL, and payment instructions without a clear verb or resource. It does not state what the tool does (e.g., 'Retrieve whale intelligence'). The title is null, and 'intel-whales' alone is insufficient to convey 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 on when to use this tool vs. siblings. The payment-related instructions imply a specific workflow, but there is no explicit statement of appropriate 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?

No annotations are provided, so the description carries full burden. It discloses key behavioral traits: unpaid calls return a payment challenge, and successful payment is required to access the data. It mentions optional headers for credits/holder tiers. However, it does not describe what the tool returns after payment, any side effects, or rate limits. This is adequate but not thorough.

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

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

The description is concise (about 50 words) and front-loaded with the cost. It conveys essential technical details without fluff. The information is packed efficiently, but the density might make it harder to parse for an AI 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?

With no output schema, the description should explain return values, but it does not. It also lacks a clear statement of the tool's purpose beyond 'intel/security route'. The 5 parameters are partially explained, but the nested 'body' object is incompletely described. Given the complexity (payment flow, multiple payment methods), the description is insufficient for full automated use.

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

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

Schema coverage is 100%, so baseline is 3. The description adds context by explaining the default body and the role of paymentSignature (omit to receive challenge). It also clarifies creditsWallet and soonHolderWallet as payment alternatives. However, it does not detail the internal structure of the 'body' parameter beyond the 'limit' default, and it does not elaborate on agentId's purpose.

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

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

The description clearly states the tool's function: a paid intel wire endpoint (POST to https://conc-exe.xyz/api/concierge-intel-wire) with a cost and default body. The verb 'intel-wire' and the mention of 'intel/security route' indicate it provides intelligence data. However, it does not explicitly differentiate from sibling intel tools like intel_desk_brief or intel_listing, though the payment model is a distinguishing factor.

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 guidance on payment methods (x402, TCX credits) and explains that unpaid calls return a PAYMENT-REQUIRED response. It implies usage involves selecting a payment method or providing headers. However, it does not specify when to use this tool over other intel tools, nor does it mention any prerequisites or limitations.

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 reveals that this is a paid API (x402 or TCX credits) and that unpaid calls return a payment challenge. This is valuable behavioral context in the absence of annotations. However, it does not disclose other behavioral traits like rate limits, authentication requirements beyond payment, or what a successful response contains.

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

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

The description is concise (two sentences) and efficiently conveys the endpoint, pricing, default body, and payment options. It is front-loaded with the most critical information. Minor structure improvements could be made, but it is well above the average in compactness.

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 describe what a successful response looks like (e.g., yields data format). The only response context is the payment challenge for unpaid calls. This leaves a significant gap for an agent using 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?

The input schema provides 100% description coverage for all 5 parameters. The tool description adds the default body value and mentions payment parameters, but this adds minimal meaning beyond what the schema already provides. 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 name 'intel_yields' and default body (meteora) imply yield intelligence, but the description lacks an explicit verb or clear statement of what the tool returns. The pricing and endpoint are mentioned, but the core function is implied rather than stated.

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 its many siblings (e.g., intel_meteora, intel_tvl, intel_macro). No prerequisites or exclusions are provided, making it difficult for an agent to decide when to invoke this tool.

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

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

With no annotations, the description carries full burden. It discloses pricing, payment flows, and that unpaid calls return a payment challenge. However, it does not describe what the scan does beyond the endpoint or what the response contains.

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, packing essential details (endpoint, default body, payment) into a single paragraph with no fluff. Could benefit from minor restructuring (e.g., separating payment info), 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?

No output schema, and the description fails to describe what a successful scan returns (e.g., vulnerability report). It only mentions payment failure responses. For a complex tool with 5 params and nested objects, this is incomplete.

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

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

Schema coverage is 100%, so baseline is 3. The description adds value by providing the default body, explaining paymentSignature omission behavior, and clarifying alternative payment methods (creditsWallet, soonHolderWallet).

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

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

The description clearly states it is a security deep scan with a POST endpoint and default body. The name 'deep_scan' hints at a more thorough scan than siblings like security_scan, but explicit differentiation is missing.

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

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

No explicit guidance on when to use this tool vs. alternatives (e.g., security_scan). The description mentions payment requirements but does not clarify use cases 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 convey all behavioral traits. It discloses payment requirements (x402 or credits) and the response for unpaid calls (PAYMENT-REQUIRED accept). However, it fails to describe the core action (e.g., whether it reads or modifies data, what the success response contains), which is a significant 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 is concise, fitting all information into a single paragraph without redundancy. It leads with the name and price, followed by endpoint, default body, and payment behavior. However, it could be more structured with separate sections 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?

Given the lack of an output schema, the description should explain what the tool returns upon successful payment, but it only mentions unpaid responses. The core functionality (security headers analysis) is not described, and the payment flow details overshadow the main purpose, leaving the agent underinformed.

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

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

Schema coverage is 100%, so each parameter already has a description in the schema. The tool description does not add extra semantic value beyond what the schema provides. It mentions the default body but does not explain parameter formats or constraints further.

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. The name suggests it involves security headers, but the text focuses on pricing, endpoint, and default body without clarifying the primary action (e.g., retrieving or analyzing security headers). This vagueness makes it difficult for an agent to understand the tool's core 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 on when to use this tool versus its siblings (e.g., security_scan, security_deep_scan). There are no contextual clues about prerequisites, appropriate scenarios, or exclusions, leaving the agent with no decision support.

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

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

No annotations exist, so the description must disclose behaviors. It notes that unpaid calls return payment-required accepts and describes payment options. However, it does not cover success behavior, idempotency, side effects, or response format.

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 paragraph that efficiently packs endpoint, pricing, default body, and payment notes. It is concise but could be better structured with separate 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?

With 5 parameters including nested objects and no output schema, the description explains the endpoint and payment flows but omits success response details and deeper parameter context. Some gaps remain.

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 the default body example but does not elaborate on parameter meaning beyond what the schema already provides.

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

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

The description identifies a POST to a security-readiness endpoint with a default body, making the action clear as a security check. However, it mixes in pricing and payment details, and doesn't explicitly state what 'security readiness' means or the expected outcome.

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 tools like security_scan or security_headers. No alternatives or exclusions are mentioned.

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

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

The description discloses the cost, endpoint, and default body, and explains the payment flow. However, it does not describe what the scan actually does (e.g., vulnerability detection, port scanning), what results are returned, or any side effects. No annotations are present, so the description carries full burden for behavioral transparency.

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

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

The description is a single paragraph combining cost, endpoint, body, and payment details. It is relatively concise but could be better structured with separate sections for clearer readability.

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

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

The description lacks key details about the scan's purpose, what the allowlist does, and the nature of the output. With no output schema and no annotations, the description does not provide enough context for an agent to understand the tool's full capabilities and requirements.

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

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

Schema description coverage is 100%, but the descriptions are brief. The tool description adds significant context by providing the default body example and explaining the payment flow, including how omitting paymentSignature triggers a payment challenge. This adds 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 clearly states it is a security scan tool with a specific endpoint and default body, indicating it scans a target URL with an allowlist and authorization. It is distinct from sibling tools like security_deep_scan and security_headers by its endpoint and pricing, but it does not explicitly differentiate itself.

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

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

The description mentions payment requirements and that unpaid calls return payment challenges, but it does not provide guidance on when to use this tool versus siblings. No context on what scenarios this scan is appropriate for.

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