Triage x402 payment surface

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive. The description adds explicit guarantees that no X-PAYMENT, wallet signatures, API keys, private tokens, or paid calls are sent, plus lists return content. No contradiction.

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: first states the core action, second lists outputs and exclusions. No redundant text, well 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?

Given the read-only, open-world nature and absence of output schema, the description is complete: it explains what the tool does, what it returns, and what it deliberately avoids sending. No critical gaps.

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 meaningful descriptions. The description adds no extra parameter-specific guidance beyond what the schema provides, so baseline 3 is appropriate.

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

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

The description uses a specific verb phrase ('Run a no-payment external pass') and lists concrete resource types (x402, MPP, Pay.sh, OpenAPI, manifest, HTTP 402 endpoint). It distinguishes itself from siblings by emphasizing 'no-payment' and 'triage' versus watching or paid paths.

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 for use: a single public endpoint, no payment, external triage pass. It does not explicitly name alternative sibling tools or exclude cases, but the scope is well defined.

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