vouch

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

With no annotations provided, the description must fully bear the burden of behavioral disclosure. It reveals that the report updates a shared reputation graph, but does not mention whether the action is reversible, whether authentication is needed, what happens after submission, or any rate limits. 'Free' is minor and does not compensate for these 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 a single, front-loaded sentence that moves from action to purpose, followed by a standalone 'Free.' note. It is efficient with no redundant phrasing, and the most important information appears first.

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 flag/vouch tool, the description covers the core action and its intended consequence, but leaves gaps: return values, permissions, reversibility, and how the report is later used are not addressed. With no annotations or output schema, the description is minimally viable 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?

Schema description coverage is 0%, so the description must compensate for missing parameter documentation. It adds meaning to 'kind' by explaining 'flag' as 'scam/bad actor' and 'vouch' as 'trustworthy', and implies 'target' is a host. However, it gives no semantics for the optional 'reason' parameter, and the expected format of 'target' remains ambiguous.

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 ('Report') with a clear resource ('a host') and outcome ('flag' or 'vouch'), and explains the effect on Vouch's reputation graph. It effectively distinguishes the tool from its sibling 'vouch_score', which likely reads rather than writes reputation.

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 when you want to submit a reputation report, but it does not explicitly state when to use this over 'vouch_score' or provide any exclusions. The phrase 'for everyone's future payment-trust checks' gives context, but there is no direct alternative 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, the description carries the full burden. It discloses detection methods (threat feeds, heuristics, reputation graph), the output format, and the free vs. paid distinction (free lacks signed attestation). It does not cover error handling or data retention, but the core behavior is well explained.

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

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

The description is three sentences, each serving a distinct purpose: purpose, usage guidance, and free/paid alternative. It is front-loaded with the main action and contains no 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?

For a simple tool with one parameter and no output schema, the description fully covers what it returns (score and risk band), the threat detection logic, and the appropriate usage context. It also mentions the paid alternative for richer output, making it complete for an agent to decide when to use it.

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

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

The schema already provides 100% coverage for the single 'target' parameter with the description 'Counterparty URL or hostname.' The description repeats this but adds no new semantics, so the baseline score of 3 is appropriate.

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

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

The description clearly states the tool's primary function ('Check whether a counterparty is SAFE TO PAY'), specifies the input (URL or host), and describes the output (0-100 trust score and risk band). It also distinguishes this free lightweight check from the paid endpoint that provides full reasoning and attestation.

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 explicit when-to-use guidance: 'Call this before paying any merchant, API, agent, or x402 resource.' It also gives a clear alternative for when more detail is needed (paid POST /v1/check endpoint), which effectively tells users when not to use this tool.

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