SENTINEL Compliance Intelligence

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

No annotations are provided, so the description carries the full burden. It adds valuable non-obvious context by disclosing the exact cost and payment method ($0.001 USDC via x402), which is a critical behavioral trait. The verb 'Get' implies a read-only operation. It does not mention auth requirements, rate limits, or error behavior, but for a simple lookup tool this is reasonable.

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

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

The description is two sentences, front-loaded with the primary purpose and followed by a concise cost note. No filler or redundant information; every word contributes to understanding the tool.

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

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

For a single-parameter tool with no output schema, the description provides sufficient context: it specifies the tool's purpose, coverage (179 countries), data sources, and cost. It does not describe the return format, but the tool name and description clearly imply a risk score, making it complete enough for an agent to select and invoke correctly.

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

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

The input schema for country_code has 100% coverage, including ISO 3166-1 alpha-2 format and examples (MU, US, RU, IR). The description does not add additional parameter semantics beyond what the schema already provides, so the baseline score of 3 applies.

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

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

The description clearly states the tool's function with a specific verb ('Get') and resource ('composite risk score for any of 179 countries'), and names the three data sources (FATF grey/blacklist, CPI, Basel AML Index). This distinguishes it from sibling tools like compliance_watchlist or country_brief, which serve different 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 implies usage for country-level compliance risk assessment but does not explicitly state when to use it instead of alternatives such as country_snapshot or due_diligence. No exclusions or alternative tool references are provided, so guidance is only implied.

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

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It does disclose a key behavioral trait: the cost ($0.005 USDC via x402), which is valuable context. However, it does not mention potential output format, API errors, rate limits, or any side effects. Since 'Search' implies a read-only operation, the transparency 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 one concise sentence that packs two pieces of essential information: what it searches and the cost. Every word contributes, with no filler or redundancy. It is appropriately sized for the tool's simplicity.

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 is a simple single-parameter search with no output schema, the description is mostly complete. It states the action, target, and cost. The only gap is not describing what the result looks like, but for a search tool, the return is likely evident. The cost disclosure adds completeness beyond the minimum.

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

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

The input schema already has a description for the 'query' parameter ('Entity or person name to search') with 100% coverage. The tool description does not add additional parameter semantics beyond indicating that the search is for Mauritius FSC/ICIJ, which is implicit in the purpose. Baseline 3 is appropriate as the schema handles the param documentation.

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

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

The description clearly states the tool's function with a specific verb ('Search') and resource ('Mauritius FSC registry + ICIJ offshore leak connections'). This distinguishes it from sibling tools like compliance_watchlist or compliance_jurisdiction_risk, which are more general. The purpose is unambiguous and directly tied to the tool's name.

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

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

The description implies usage context by specifying the search target (Mauritius FSC and ICIJ leaks), but it does not explicitly state when to choose this tool over alternatives or mention exclusions. It gives enough context to infer appropriate use but lacks explicit guidance or named 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 provided, the description carries the full burden of disclosure. It adds meaningful behavioral context by disclosing the exact data sources screened and the cost per invocation ($0.003 USDC via x402). It does not mention output structure or failure cases, but the identified behavior is clear and honest for a screening 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 two sentences long, front-loads the core action, lists the specific sanction lists, and provides the critical cost information. Every word adds value, and there is no filler or repetition of schema details.

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

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

Given the tool's moderate complexity, the description is largely complete: it states the purpose, data sources, and cost. There is no output schema, so a brief mention of what the response contains (e.g., matches or risk status) would improve completeness, but the description still provides enough for correct 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?

The input schema already provides 100% coverage for both parameters ('address' and 'chain'), including valid chain hints and default values. The description adds no additional parameter-level information, so it meets the baseline but does not exceed it.

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

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

The description uses a specific verb 'Screen' and identifies the resource as 'blockchain wallet address' against 'sanctioned/blacklisted crypto addresses', listing concrete sources (OFAC SDN, USDT Blacklist, etc.). This clearly distinguishes it from sibling tools like compliance_wallet_entity or compliance_watchlist, which likely target different aspects.

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

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

The description implies the tool should be used when you need to screen a wallet address against sanctions lists, and it mentions the cost model. However, it does not explicitly state when not to use it or mention alternative tools for related compliance checks (e.g., entity screening or jurisdiction risk), leaving room for ambiguity in 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?

With no annotations, the description carries the full burden of behavioral disclosure. It adds useful details about cost ($0.003 USDC via x402) and the cross-referencing nature, but it does not disclose potential side effects, authorization requirements, rate limits, or return format. The cost disclosure is a positive, but other behavioral aspects remain 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 three concise sentences, front-loaded with the core purpose ('Compound Web2+Web3 screen'), and every sentence adds value: function, integration, and cost. No redundant or filler content.

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

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

The description conveys the core purpose and cost but lacks details about output structure, error handling, or edge cases (e.g., what 'convergence detection' returns, timeout behavior). With no output schema and no annotations, the description should provide more context to fully prepare the agent. It's adequate but not comprehensive.

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 100% of parameters with descriptions, so the schema does the heavy lifting. The description adds a high-level mapping ('wallet address + entity name') but does not elaborate on parameter syntax, defaults, or interactions beyond what the schema already states. Baseline 3 is appropriate given complete schema coverage.

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

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

The description clearly states the tool's function: a combined Web2+Web3 screen using wallet address and entity name with convergence detection. It distinguishes from sibling tools like compliance_wallet (wallet-only) and compliance_watchlist (generic list) by emphasizing the compound nature and the bridge to traditional sanctions databases.

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

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

The description provides clear context for when to use the tool: when needing to combine a wallet address with an entity name and detect convergence across blockchain and traditional databases. However, it does not explicitly name alternatives or state when not to use it, leaving some room for inference based on sibling tool 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?

No annotations are provided, so the description must fully disclose behavior. It adds the cost ($0.005 USDC) and enumerates the watchlist sources, but it does not explain what the tool returns (e.g., matches with confidence scores), rate limits, or potential false positive handling. The absence of output schema amplifies 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, information-dense sentence that includes purpose, scope, and cost without extraneous wording. It is well-structured and front-loaded.

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

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

The tool has no output schema and no annotations, yet the description does not describe the expected response format or the behavior when no matches are found. It also lacks information on pagination or error handling. Given the moderate complexity, the description is not fully complete for an agent to anticipate the tool's 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?

All three parameters are already described in the schema with complete coverage (100%). The description adds no parameter-specific semantics beyond the schema, so it meets the baseline of 3 but does not elevate it.

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

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

The description uses a specific verb ('Screen') and clearly identifies the resource ('global watchlist records'), listing major list types (OFAC, UN, EU, PEP, Interpol, crypto). This distinguishes it from sibling compliance tools like compliance_wallet or transaction_screen.

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

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

The description implies when to use (for screening entities against global watchlists) but does not explicitly state when not to use or mention alternatives. There is no exclusion criteria or comparison to sibling tools like transaction_screen or travel_rule_screen.

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

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

No annotations are provided, so the description carries the full burden. It discloses that the tool costs $0.010 USDC, is an aggregated call replacing 8 APIs, and includes specific oracle feeds for Mauritius. It does not mention side effects, prerequisites, or response format, but for a read-only intelligence brief, this is adequate.

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

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

The description is three sentences, front-loaded with the core purpose, and every sentence adds value: the scope for Mauritius, the aggregation benefit, and the cost. 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?

With one parameter, no output schema, and no annotations, the description covers the tool's purpose, scope, cost, and aggregation behavior. It could be more explicit about the structure of the brief or potential limitations, but given the simplicity of the tool, it is sufficiently complete.

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

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

The input schema already provides a complete description of the single country_code parameter (ISO 3166-1 alpha-2 with examples). The tool description adds no additional parameter meaning beyond the schema, so with 100% schema coverage, the baseline of 3 applies.

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

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

The description clearly states the tool produces a 'Complete country intelligence brief' combining compliance risk assessment and live economic data, and specifically notes it includes all 7 oracle feeds for Mauritius, distinguishing it from narrower sibling tools like compliance_jurisdiction_risk or forex_rates.

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 by saying 'Replaces 8 API calls,' indicating it's for consolidating data, and notes the cost. However, it doesn't explicitly name alternative tools or when to avoid using it, so it lacks explicit exclusions.

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

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

No annotations are provided, so the description carries the full burden. It discloses the cost ($0.005 USDC via x402) and the aggregation behavior (ALL feeds), but lacks details on data freshness, response format, or error handling. This is minimal disclosure for a tool with no annotation support.

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

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

The description is a single, front-loaded sentence that clearly states the main benefit and cost. Every word is purposeful, with no filler or 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?

For a zero-parameter tool, the description is adequate for initial selection and use. However, it does not specify which feeds are included or what the response structure looks like, which would be helpful given there is no output schema.

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

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

There are zero parameters and the schema is an empty object, so the baseline is 4. The description does not need to add parameter semantics since none exist.

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

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

The description clearly states the tool's function with a specific verb 'Get' and resource 'complete Mauritius economic pulse'. It distinguishes itself from siblings by emphasizing 'ALL feeds in one call', contrasting with the specialized sibling tools like forex_rates and fuel_prices.

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

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

Usage is implied: use when a comprehensive economic overview of Mauritius is needed. However, there is no explicit when-not to use it or mention of alternatives, such as using specific sibling tools for individual data feeds.

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 and does well by disclosing the packaged scope, the cost of $0.010 USDC via x402, and the efficiency benefit of replacing 5 calls. However, it does not describe the output format or limitations of the composite risk score, leaving some behavioral detail unspecified.

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 consists of two compact sentences that front-load the package components and then add cost and efficiency. Every word contributes meaningful information with no redundancy or fluff.

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

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

Given the complexity of this compound tool and no output schema, the description gives a solid high-level overview but omits details about the composite risk score's meaning, return value, or what 'forex context' entails. This is adequate but has clear gaps for an agent needing to trust or interpret the 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 description coverage is 100% for both parameters, so the baseline is 3. The description adds the phrase 'forex context' which loosely maps to include_forex but does not enrich parameter semantics beyond what the schema already states.

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

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

The description clearly identifies a compound screening package with specific components (watchlist, jurisdiction risk, Mauritius FSC, forex, composite risk) and positions it as an aggregation that replaces five separate API calls. This distinguishes it from sibling tools like compliance_watchlist or compliance_jurisdiction_risk.

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

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

The description implies usage when comprehensive due diligence is needed and mentions it replaces 5 separate API calls, but it does not explicitly state when to use individual compliance tools instead or provide exclusions. This is implied usage rather than clear guidance.

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

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

No annotations are provided, so the description carries the full burden. It discloses the core behaviors (registry lookup, screening, JWT attestation) and notes the tool is 'FREE', but it does not mention potential side effects, data handling, rate limits, or whether the JWT attestation involves any write/state-changing action. This is moderate transparency for a read-oriented lookup 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 concise sentence that packs in the registry, screening, attestation, return fields, and cost. It is front-loaded with the key concept 'Know Your Agent' and has no redundant filler.

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 single-parameter tool with no output schema, the description provides a solid overview of what it returns (registration status, operator wallet, screening results, coldStartSignals) and its purpose. It lacks some details like exact input format quirks or broader capability boundaries, but it is sufficient for tool selection.

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

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

The single parameter 'address' is fully described in the schema with an example, and the description adds no extra information about the parameter itself. Since schema coverage is 100%, the baseline of 3 is appropriate; the description does not need to compensate.

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

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

The description clearly defines the tool's purpose as an ERC-8004 registry lookup combined with sanctions screening and signed JWT attestation. It names specific outputs like 'agent registration status', 'operator wallet', and 'coldStartSignals', which effectively distinguishes it from siblings such as compliance_wallet or transaction_screen.

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 checking any wallet address against an agent registry and sanctions screening, but it does not explicitly state when to use this tool versus alternatives like compliance_wallet or travel_rule_screen. No exclusions or comparative guidance are given.

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

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

No annotations are provided, so the description carries the burden. It implies a read-only 'Get' operation and lists return contents, but it does not disclose whether the data is static, real-time, or requires any authentication. The 'FREE' note adds a small behavioral/economic trait, but overall transparency is minimal.

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

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

The description is a single, front-loaded sentence with no fluff. It immediately states the verb and resource, lists specifics, and ends with a brief 'FREE.' All content earns its place.

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

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

Given the low complexity (no parameters, no output schema), the description covers the essential purpose and expected return content. However, it could briefly note that this is a read-only operation or that capabilities may vary by jurisdiction (given sibling tools like compliance_jurisdiction_risk), so it is not fully complete.

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

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

The input schema is empty (0 parameters), yielding a baseline of 4. The description correctly includes no parameter details, and there is nothing misleading. As there are no parameters to explain, the description adequately satisfies this dimension.

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

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

The description starts with a clear verb 'Get' and specific resource 'SENTINEL facilitator capabilities', followed by a concrete list of what is included (payment schemes, networks, assets, compliance features). This distinguishes it from siblings like facilitator_kya by focusing on capabilities rather than KYC or compliance checks.

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

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

The description provides no guidance on when to use this tool versus alternatives. It does not mention any context, prerequisites, or exclusions. The 'FREE' note hints at a low cost but does not explain when to invoke this tool over 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?

With no annotations, the description carries the burden of behavioral disclosure. It explicitly mentions a cost of $0.001 USDC via x402, which is a significant behavioral trait. It also indicates a read-only action via "Get," but omits details about rate limits, response behavior, or authentication requirements.

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

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

The description is extremely concise, consisting of two short sentences. It front-loads the core action and resource, and every word earns its place. No unnecessary elaboration.

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

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

For a simple tool with one optional parameter and no output schema, the description is adequate but leaves the return format unstated. It does not explain what the exchange rates represent (e.g., base currency reference) nor how many results to expect, which would be helpful given the paid nature.

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 fully documents the single optional parameter with 100% coverage. The description does not add any additional meaning beyond the schema, so it stays at the baseline for high schema coverage.

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

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

The description uses a specific verb ("Get") and identifies an exact resource ("MUR exchange rates from Bank of Mauritius"). This clearly distinguishes it from sibling tools, none of which directly provide exchange rates.

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: if you need MUR exchange rates from Bank of Mauritius, use this tool. However, it provides no explicit guidance about when to use this versus alternative tools, nor any exclusions or alternative recommendations.

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 of $0.001 USDC via x402, which is a behavioral trait not covered by annotations (none provided). However, it does not mention failure modes, caching, or output format, leaving some transparency gaps.

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

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

The description is concise and front-loaded: it states the purpose in the first clause and the cost in the second. No unnecessary words or repetition.

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

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

For a simple read-only tool with one optional parameter, the description covers the essential context: what data is returned, from where, and the cost. It does not describe the output structure, but this is not critical given the simplicity and lack of an output schema.

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

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

The input schema fully documents the optional 'product' parameter with its enumerated values (mogas, gasoil, lpg), so schema coverage is 100%. The description adds no extra meaning beyond the schema, which is acceptable but not above baseline.

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

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

The description clearly states the tool retrieves petroleum retail prices from STC Mauritius. The verb 'Get' is specific and the resource is well-defined, distinguishing it from sibling tools like forex_rates or weather.

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

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

The description gives clear context: use this tool when you need petroleum retail prices from STC Mauritius. It does not explicitly mention alternatives or exclusions, but the specificity of the source implies the appropriate use case.

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

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

With no annotations provided, the description carries the transparency burden. It discloses the cost ($0.001 USDC via x402) and dataset count, which are useful, but it does not mention expected result format, rate limits, authentication requirements, or error behavior. For a paid search tool, this is minimal behavioral disclosure.

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: two sentences that provide the key scope and cost information. Every word is purposeful, with no redundancy or filler.

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

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

For a simple one-parameter search tool, the description covers the essential scope and payment requirement. However, the lack of annotations and absence of any output schema mean the agent has no hint of return structure or failure modes, leaving the description merely adequate.

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

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

Schema coverage is 100% and the single parameter 'q' has a clear description ('Search query for government datasets'). The main description adds no extra parameter semantics, so the baseline of 3 applies since the schema already fully documents the parameter.

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

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

The description clearly identifies the tool as a search over Mauritius government datasets, using a specific verb ('Search') and resource ('Mauritius government datasets'), with the added detail of 812+ datasets. It does not explicitly differentiate from sibling tools by naming alternatives, but the purpose is unambiguous.

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

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

There is no guidance on when to use this tool versus alternatives, nor any mention of exclusions or prerequisites beyond the cost. The description states what the tool does but not when it should be selected among the many sibling compliance and country-related 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 explicitly discloses a critical behavioral trait: the tool costs $0.002 USDC via x402. This is important for an agent deciding whether to call the tool. However, it does not mention response format, rate limits, or authorization details, so it is not fully transparent.

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

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

The description is a single, front-loaded sentence with zero wasted words. It opens with the action and resource, then attaches the cost detail. Excellent structure.

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

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

Given the tool's simplicity (one optional parameter), the schema covers all parameter details, and the description covers purpose and cost. No output schema exists, but for a data retrieval tool, the description and schema together are complete enough.

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

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

Schema coverage is 100%, and the schema already lists all valid indicator values. The description adds no additional meaning beyond the schema, only examples. Baseline of 3 is appropriate as the description does not hinder understanding but adds little.

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

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

The description clearly states the tool retrieves Mauritius macro-economic indicators with specific examples (GDP, CPI, unemployment, tourism). The verb 'Get' identifies the action, and the resource is well-defined, distinguishing it from sibling tools like country_brief or govdata_search.

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

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

No guidance is provided on when to use this tool versus alternatives. There is no mention of preferred use cases, exclusions, or comparison with sibling tools. The purpose implies usage for macro indicators, but no explicit context 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?

With no annotations, the description carries the full burden. It does disclose a significant behavioral trait: 'Costs $0.002 USDC via x402' — important for an agent deciding whether to invoke. The verb 'Get' implies a read-only operation, but no further details are given about return format, error handling, or rate limits. This is adequate but not rich.

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

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

Two sentences, perfectly front-loaded: the first states the purpose, the second the cost. No filler or redundant information. Every word earns its place, fulfilling conciseness expectations.

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, no-parameter getter with no output schema, the description captures the essential data points (Key Repo Rate and Prime Lending Rates) plus the cost. It could add update frequency or units, but given the tool's simplicity and the lack of output schema, it is reasonably complete. Sibling differentiation is absent, which slightly lowers the score.

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 tool has zero parameters, so schema coverage is 100% by default. The baseline for 0 params is 4, and the description doesn't need to elaborate on parameters. It does not attempt to describe non-existent parameters, so the score fits.

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

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

The description explicitly states the tool's function: 'Get Bank of Mauritius Key Repo Rate and Prime Lending Rates.' It uses a specific verb ('Get') and resource (the two rates), distinguishing it from sibling tools like macro_indicators or forex_rates by naming the exact data source and 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 is provided on when to use this tool versus alternatives (e.g., macro_indicators might also contain repo rates). The description merely states what it does, leaving the agent to infer usage context. There is no mention of exclusions or preferred scenarios.

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

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

No annotations are provided, so the description carries the burden of disclosing behavioral traits. It mentions the cost of $0.003 USDC via x402 and implies a read-only re-screening operation, but it does not explicitly state whether the tool makes any modifications or requires specific permissions. This is a partial disclosure but not comprehensive.

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

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

The description is two sentences, front-loaded with the core purpose and followed by the cost detail. Every word contributes value without redundancy, making it appropriately concise and well-structured.

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

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

For a simple tool with one parameter and no output schema, the description adequately covers what the tool does and the cost associated. It leaves some ambiguity about the exact format of the returned alert state, but given the straightforward nature of the operation, the description is nearly complete. A minor gap is the lack of explicit alternative guidance, but the sibling context helps fill that.

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

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

The input schema already provides a full description of the subscription_id parameter, including its format (MON-XXXXXX-XXXXXXXX), so the description adds no additional semantic value. With 100% schema coverage, a baseline score of 3 is appropriate; the tool description does not need to repeat what the schema already defines.

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: 'Check monitoring subscription status' and further specifies it re-screens the subscribed entity against the latest database to return the current alert state. This goes beyond a simple verb-noun pairing and distinguishes it from sibling tools like monitor_subscribe, which handles creation rather than status checks.

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

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

The description gives clear context for when to use the tool: to check the status of a monitoring subscription and retrieve the latest alert state. It does not explicitly state when not to use it or name alternatives, but the purpose is evident enough to avoid confusion with the subscription creation 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 the full burden. It discloses key behaviors: 30-day duration, status flip to 'alerted', optional webhook, and cost ($0.010 USDC). However, it omits details like expiration/renewal behavior, cancellation, or what the initial 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?

Three sentences, each delivering distinct value: subscription action, alert behavior, webhook and cost. No fluff, front-loaded with the primary verb and resource.

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

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

The description covers the core transaction: what is monitored, duration, alert status, and cost. However, with no output schema, it fails to clarify the return value (e.g., subscription ID) or post-subscription management (cancel/renew). This is a notable gap for a paid subscription tool.

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

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

Schema coverage is 100%, so parameters are fully documented. The description adds context about wallet/entity (type) and webhook_url, but does not exceed the schema for chain or label. This matches the baseline of 3 when the schema does the heavy lifting.

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: 'Subscribe a wallet or entity for 30-day continuous monitoring.' This is a specific verb (subscribe) with a resource (wallet/entity) and scope (30-day), distinguishing it from siblings like monitor_check or compliance_watchlist.

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

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

The description implies use for ongoing monitoring over a fixed period, with alerts on blacklist hits, and optional webhooks. It does not explicitly name alternatives (e.g., monitor_check for one-time checks), but the context is clear enough that an agent can infer when to use it.

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

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

No annotations exist, so the description carries the burden. It discloses the cost ($0.015 USDC via x402), the traversal behavior, and the output (risk network map with composite scoring). However, it omits potential rate limits, error conditions, or the exact format of the map, leaving some behavioral ambiguity.

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

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

The description is two sentences, front-loaded with the core function, followed by a value proposition and cost. Every clause earns its place with no filler or 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?

For a tool with no output schema, the description explains the output (risk network map with composite scoring) and mentions cost and the replacement of manual work. It doesn't cover performance or failure modes, but for a 2-parameter tool with clear purpose, this is reasonably complete.

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

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

Schema description coverage is 100%, so the baseline is 3. The description adds context by linking 'depth' to 'traverses entity relation graph' and 'query' to 'Entity name to scan,' but it doesn't significantly enhance the 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 uses specific verbs and nouns: 'finds all watchlist hits, traverses entity relation graph, screens connected entities, produces risk network map with composite scoring per node.' This clearly differentiates it from sibling tools like compliance_watchlist (simple hit check) or due_diligence, emphasizing graph traversal and network output.

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

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

The description implies when to use it: when you need entity relationship intelligence and want to avoid 10-20 API calls plus manual analysis. It doesn't explicitly name alternatives or exclusions, but the 'replaces' phrasing gives strong usage context. However, it could be more explicit about when not to use it.

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

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

The description discloses a notable behavioral trait: the cost of $0.001 USDC via x402. Since no annotations are provided, this adds transparency about payment requirements. However, it does not mention output format, error behavior, or other potential side effects, so coverage is partial.

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 exceptionally concise: two sentences with the first stating purpose and the second stating cost. Every word earns its place, and it is front-loaded with the 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?

The tool is simple with one optional parameter and no output schema, so the description covers the basics. However, it omits the additional index options (sem10, demex) that appear in the schema, and it does not describe the return format. This is a minor gap for such a lightweight tool.

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

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

The schema fully describes the only parameter ('index' with options semdex, sem10, demex and 'omit for all'), so the baseline is 3. The description adds no extra parameter semantics beyond the schema, which is acceptable given the 100% schema coverage.

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

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

The description clearly states a specific verb ('Get') and resource ('SEMDEX and SEM indices from Stock Exchange of Mauritius'), which immediately conveys the tool's function. This distinguishes it from sibling tools like forex_rates and fuel_prices by specifying the exact market and indices.

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

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

The description implies when to use the tool (when Mauritian stock market indices are needed), but it does not explicitly mention alternatives or when not to use it. There is no comparison with sibling tools or mention of exclusions, leaving usage context only implicit.

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 cost ($0.008 USDC via x402), aggregation behavior ('Replaces 6 API calls'), and decision output (PROCEED/REVIEW/FLAG/BLOCK). While it doesn't mention auth or side effects, the tool is a read-only screening operation, making the disclosed cost and return type key transparency elements.

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

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

Two sentences, front-loaded with the primary purpose, followed by specific actions, output, and cost. Every phrase contributes meaningful information without fluff, achieving high density and clarity.

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

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

Despite lacking an output schema, the description clearly states the return type (PROCEED/REVIEW/FLAG/BLOCK recommendation). It also explains the scope (watchlist, jurisdiction, forex) and the operational benefit. For a composite tool, this is sufficient for an agent to select and invoke it, though a bit more detail on the response structure would be ideal.

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

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

Schema covers 100% of parameters with descriptions. The tool description adds semantic context by implying relationships: sender/receiver names for watchlist, country codes for jurisdiction risk, and currency codes for forex corridor rate. This mapping enriches beyond the raw schema, though not exhaustively.

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

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

The description clearly states the tool's purpose: 'Cross-border transaction pre-screening' with a specific verb ('checks') and resource (sender/receiver, watchlists, jurisdiction, forex). It lists concrete actions and output types (PROCEED/REVIEW/FLAG/BLOCK), distinguishing it from sibling tools like compliance_watchlist or compliance_jurisdiction_risk by being a composite pre-screening tool.

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

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

The description implies usage context by stating it 'Replaces 6 API calls', signaling that this tool is a more efficient alternative to multiple individual compliance calls. It doesn't explicitly name alternatives or when-not-to-use, but the functional coverage (watchlist, jurisdiction, forex) makes it clear this is the go-to for a consolidated cross-border screening.

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 a cost of $0.005 USDC via x402, the return of a structured compliance packet with unique packetId, and the one-call scope. It doesn't cover failure modes or authentication, but the added cost/output details go beyond schema.

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

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

Two sentences, front-loaded with the compliance framework, and each sentence serves a purpose: what it does, what it returns, and what it costs. Zero extraneous wording.

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 8 parameters, no output schema, and no annotations, the description provides essential context: purpose, output format (compliance packet with packetId), and cost. It lacks operational details like authentication prerequisites or error behavior, but the core information for selection and invocation is present.

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

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

Schema coverage is 100%, so baseline is 3. The description groups parameters into categories (wallets, entity names, jurisdictions) but does not add per-parameter semantics beyond what the schema already provides. It adds no syntax or format details, so it meets the baseline without exceeding it.

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 screens both originator and beneficiary wallets, entity names, and jurisdictions for FATF R16 Travel Rule compliance in one call. This specific verb+resource distinction differentiates it from sibling tools like compliance_wallet or transaction_screen.

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

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

Provides clear context: FATF R16 Travel Rule compliance and the value of a single-call screening for both parties. However, it does not explicitly mention when not to use it or alternatives such as compliance_wallet or compliance_watchlist, so a minor gap in exclusionary guidance.

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

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

With no annotations provided, the description carries the burden of behavioral disclosure. It reveals that the tool costs $0.001 USDC via x402, which is important non-obvious behavior. However, it lacks details about error handling, rate limits, or response structure, leaving some gaps for a simple 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 incredibly concise, consisting of two short sentences that state the purpose and cost. It is front-loaded with the primary action, and every word adds value with no redundant details.

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

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

For a tool with one optional parameter and no output schema, the description covers the essential information: what it does (gets weather) and the cost. The lack of return format details is acceptable given the simplicity, though a bit more context about the response could improve completeness.

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

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

The input schema already provides a comprehensive description of the station parameter, including examples and default behavior (omit for all). The tool description adds no extra meaning beyond the schema, so a baseline score of 3 is appropriate given 100% schema coverage.

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

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

The description clearly states the tool's function with a specific verb ('Get') and resource ('current weather from all Mauritius Met Service stations'). It distinguishes itself from sibling tools, which focus on compliance, finance, and other domains, leaving no ambiguity.

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

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

The description provides clear context for when to use the tool (to retrieve current weather) and mentions the cost and payment method (x402), which is a usage consideration. It does not explicitly discuss alternatives, but no sibling tool provides weather data, so the guidance is sufficient.

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