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

No annotations are provided, so the description must carry the behavioral disclosure burden. It does not explicitly state whether the audit is read-only, whether it makes external network calls, whether it can be safely repeated, or what side effects 'forceRefresh' might have at the mint.

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 front-loaded sentence with no filler or repetition. 'Audit Cashu mint health' leads with the action and resource, then specifies the exact audit dimensions.

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 two-parameter tool with complete parameter documentation, the description is adequate for selection and basic invocation. However, there is no output schema and no mention of what the returned audit result looks like or how to interpret the counterparty risk score, which leaves a meaningful gap.

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

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

Schema description coverage is 100%, so the schema already documents both mintUrl and forceRefresh fully. The description adds no additional parameter-level meaning, which is acceptable under the baseline for full 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 ('Audit'), a specific resource ('Cashu mint'), and concrete audit dimensions (health, NUT-06 status, counterparty risk score). This clearly communicates what the tool does and differentiates it from payment, routing, and identity sibling tools.

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

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

There is no guidance about when to use this tool versus the sibling tools, particularly check_trust_score which also deals with risk/trust. The description states what it does but not the conditions or scenarios that should lead an agent to select it over the 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 the burden of behavioral disclosure. 'Verify' implies a read-only operation and the description states what is returned (score 0-100 and WoT distance), but it does not mention failure modes, data sources, or whether any network/trust-service lookup is involved.

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?

A single, tightly worded sentence with no filler. The key action and target are front-loaded, and the output range is included efficiently.

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 one-parameter query tool with no output schema, the description adequately explains the input and the returned values. It could add detail about what 'Web-of-Trust distance' means or how to interpret the score, but the core information an agent needs to invoke it correctly 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 description coverage is 100%, and the description does not meaningfully add beyond the schema: both identify the pubkey as the target. The description reiterates the purpose but provides no extra syntax, formatting, or edge-case behavior for 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 names a specific action ('Verify'), a specific resource ('anti-Sybil Trust Score and Web-of-Trust distance'), and a specific target ('Nostr pubkey'). This clearly distinguishes it from the sibling tools, which are mostly payment/identity/telemetry operations.

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 makes the tool's context clear: it is for verifying anti-Sybil trust information about a Nostr pubkey. It doesn't explicitly name alternatives or exclusions, but none of the sibling tools overlap with this purpose, so the intended use is unambiguous.

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 behavioral burden. 'Get' and 'public' suggest a read-only operation, but the description does not explicitly rule out side effects, error conditions, or special behavior, leaving a mild transparency gap.

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

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

A single sentence conveys the essential information with no filler or repetition. It is appropriately sized for a zero-parameter identity getter.

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 low complexity, empty parameter schema, and lack of output schema, the description is nearly complete. It names the returned information ('public identity and npub'), though it could be slightly more explicit about the output format or exact fields.

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 and the schema is trivially 100% covered, so no parameter explanation is needed. The description adds meaning by clarifying what the no-input call returns: the agent's Nostr identity and npub.

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

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

The description names a specific verb ('Get') and a clear resource ('the autonomous agent's Nostr public identity and npub'). It is easily distinguished from siblings like pay_cashu_nutzap, check_trust_score, and get_agent_telemetry.

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 intended use is implied: call this when the agent needs its own Nostr identity or npub. However, it does not explicitly state when not to use it or compare it with alternatives, and no sibling tool serves a similar purpose.

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 only states the action 'retrieve' and the data categories, but does not mention pagination, default limits, authentication requirements, whether data is a snapshot or continuous, or any potential side effects. This is a significant gap for a data-retrieval 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, well-formed sentence with no wasted words. It is concise, though it could be slightly restructured to front-load the most critical information, but it is not verbose.

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

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

Given there is no output schema and no annotations, the description should clarify return format, pagination behavior, and any prerequisites. None of this is provided. An agent calling this tool would not know what the response structure looks like or if there are any constraints beyond the parameters.

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

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

The input schema has 100% description coverage for both parameters (limit and timeframeHours), including defaults. The tool description adds no extra meaning beyond what the schema already provides, so the 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 a clear verb ('Retrieve') and a specific resource ('agent telemetry metrics, rolling spend volume, and security events'), which distinguishes it from sibling tools like get_agent_identity and get_spending_guardrails. The purpose is unambiguous and directly actionable.

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, nor any exclusions or context for selection. While the name suggests telemetry retrieval, the description offers no explicit routing information to an agent deciding between this and 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?

With no annotations, the description carries the behavioral burden. The verb 'Check' strongly implies a read-only, non-mutating operation, and it names the specific data returned. However, it does not disclose whether any state changes occur, whether values are real-time, or whether authentication is required.

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 filler or repetition. Every word adds meaning by specifying the action, the resource, and the exact values the agent can expect.

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, read-only query with no output schema, the description provides the key conceptual return items: budget, daily limits, and remaining satoshis. It could be slightly more complete by clarifying response format or units, but 'satoshis' already removes the main ambiguity.

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 input schema is empty, so there is nothing to document. The baseline of 4 applies because the description correctly focuses on the tool's output rather than attempting to describe nonexistent parameters.

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 ('Check') and a clear resource ('current AI agent spending budget, daily limits, and remaining satoshis'). This directly distinguishes it from sibling payment, identity, telemetry, and audit tools.

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

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

The description does not state when to use this tool versus alternatives, nor does it provide exclusions or prerequisites. It implies a read-only inspection use case but never explicitly says 'use this before spending' or contrasts with siblings like get_agent_telemetry.

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 alone must disclose behavioral traits. It does state the payment sends eCash and respects guardrails, but for a money-moving operation it omits consequences like irreversibility, prerequisites, failure modes, and the quote-invoice path when cashuToken is 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?

A single sentence with no filler, front-loading the action and payment type and ending with the guardrail constraint. Every phrase contributes useful information.

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

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

Despite full schema coverage, the tool has no output schema and no annotations, so the agent is left without return-value, error, or prerequisite details. For a side-effecting payment tool, the description should at least point to guardrail checks or clarify the no-token quote behavior.

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

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

All five parameters have schema descriptions, so the schema carries the semantic weight. The description only adds high-level context (eCash, Nostr recipient, guardrails) and does not add parameter-level detail beyond the schema, which matches the baseline for 100% 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 names a specific action, 'Send', and a precise resource: an eCash NutZap payment via NIP-61 to a Nostr recipient. The eCash/NutZap phrasing differentiates it from sibling Lightning payment tools like pay_lightning_nwc.

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

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

It provides clear context for when this tool applies: eCash NutZap payments to Nostr recipients, with guardrail limits enforced. It does not explicitly name alternatives or exclusion criteria, but the payment rail is enough to route an agent away from the Lightning 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?

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only states the action without revealing any behavioral traits such as the need for a connection URI, timeout behavior, failure modes, or whether the payment is irreversible. For a mutation tool with zero annotation coverage, this is a significant gap that could lead an agent to misuse it.

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, succinct sentence that clearly communicates the core action. It is appropriately sized with no wasted words. However, it may be too terse to be helpful beyond a basic understanding, but conciseness is not the issue – it is the lack of substance that hurts the overall score.

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 a payment tool (4 parameters, no output schema, no annotations), the description is incomplete. It does not explain when to use this tool versus pay_with_nwc, does not disclose behavioral details, and does not clarify parameter semantics beyond what the schema already provides. An agent would have to infer too much from the tool name and 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?

Schema coverage is 100% – every parameter (nwcUri, invoice, timeoutMs, amountMsat) has a description in the input schema. The tool description adds no additional parameter context, so it does not improve upon the schema. Baseline 3 is appropriate when the schema handles the parameter 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 a specific action ('Pay'), a specific resource ('BOLT-11 Lightning invoice'), and the mechanism ('NIP-47 Nostr Wallet Connect'). This is precise and unambiguous. However, it does not differentiate from the sibling tool 'pay_with_nwc', which could be a broader or alternative payment tool. The name itself ('lightning_nwc') and the BOLT-11 specificity hint at a difference, but no explicit distinction is made.

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

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

No guidance is provided on when to use this tool versus alternatives. The description only states what it does, with no mention of conditions, exclusions, or when a sibling tool like 'pay_with_nwc' would be more appropriate. An agent receives no contextual hints 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?

No annotations exist, so the description carries the full behavioral burden. It does not disclose that paying is irreversible, that it spends funds, that amountless invoices require amountMsat, or how the nwcUri fallback to an environment variable behaves. The single sentence covers mechanism but not operational consequences.

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

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

The description is a single focused sentence and is easy to parse. The parenthetical 'alias' saves space but adds ambiguity, preventing a perfect score.

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 payment operation with no annotations and no output schema, the description is too thin. It omits usage selection, behavioral warnings, and any clarification of the alias relationship, leaving an agent under-informed about a financially meaningful call.

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

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

Schema description coverage is 100%, so the parameters are already fully documented. The description adds only the 'BOLT-11' context for the invoice, which is marginal value beyond the schema.

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

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

The description states a specific action ('Pay'), a specific resource ('BOLT-11 Lightning invoice'), and the transport method ('NIP-47 Nostr Wallet Connect'). It is clear on its face, though it does not explicitly differentiate itself from the sibling 'pay_lightning_nwc' beyond the parenthetical 'alias.'

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

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

No guidance is given about when to use this tool versus alternatives such as 'pay_lightning_nwc' or 'pay_cashu_nutzap'. The word 'alias' hints at a relationship to another tool, but the description never says whether this is the same operation, a fallback, or a preferred path.

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, but it only discloses that the task is 'across Nostr relays' and includes 'local fallback'. It does not mention whether this dispatches a paid bid, whether it awaits results, whether it mutates state, or what happens on failure.

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?

A single, front-loaded sentence with no filler. Every phrase ('Dispatch', 'NIP-90 DVM analytics', 'across Nostr relays', 'local fallback') contributes meaningful information without 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 annotations and no output schema, this description is too sparse. It does not explain what a DVM is, whether the tool returns results synchronously or asynchronously, when payment is involved, or how the local fallback behaves in practice. An agent has to infer significant operational context from the parameter schema alone.

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

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

Schema description coverage is 100%, so the schema already documents all five parameters. The description adds no extra parameter meaning, but per the baseline rule, this is acceptable when the schema fully covers the parameters.

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

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

The description names a specific verb ('Dispatch') and a concrete resource type ('NIP-90 DVM analytics computation task'), so an agent can tell this is for submitting analytics work to a DVM infrastructure. However, it does not explicitly differentiate from the sibling 'check_trust_score' tool, which could plausibly overlap with the 'trust-score' category.

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 such as 'check_trust_score' or any of the payment-oriented siblings. The description implies usage through its name and wording, but it does not state conditions, prerequisites, or exclusions.

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

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not reveal whether this tool actually executes a payment, only returns a selected mint, or performs external network checks. The description also omits side effects, trust-score mechanics, and what the agent should do with the result.

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 filler or repetition. It efficiently conveys the tool's core selection objective, though it could arguably expand slightly without becoming bloated.

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 that there is no output schema and no annotations, the description is too thin to fully orient an agent. It does not clarify what the tool returns, whether any payment is executed, or how the routing result should be used with sibling payment tools. An agent could reasonably misinterpret 'route ... for a payment' as meaning the tool itself sends funds.

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 all three parameters are already meaningfully documented in the schema. The description adds high-level algorithm context ('highest-trust, lowest-latency') that relates to minTrustScore and preferredMint, but it does not add per-parameter details beyond what the schema provides, matching the 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 uses a specific verb ('Route') with a clear resource ('Cashu mint') and a precise selection objective ('highest-trust, lowest-latency'). This clearly distinguishes it from sibling tools like pay_cashu_nutzap, which executes payments, and audit_cashu_mint, which audits a mint rather than selecting a route.

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

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

The phrase 'for a payment' gives useful context that this tool is part of a payment flow, but the description does not explicitly say when to use this tool versus pay_cashu_nutzap or pay_with_nwc, nor does it mention that routing should happen before the actual payment call. Usage context is implied, not stated.

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