List cp0x x402 resources

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and open-world, so safety is covered. The description adds that results carry prices and tags, which is useful since there is no output schema, but it omits pagination, result size, or any other behavioral context.

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 short sentences, zero filler, and the core purpose is front-loaded before the usage hint.

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, single-optional-param list tool with annotations covering the safety profile, this is largely sufficient; the only mild gap is the absence of return-format/pagination detail, though the description does name the fields returned.

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 only parameter (tag) is fully documented in the schema as 'Resource tag to filter by.' The description mentions tag filtering but adds no syntax, case-sensitivity, or multi-tag semantics beyond what the schema provides, so baseline 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 states a specific verb and resource ('List cp0x x402 resources') plus the returned fields ('with prices and tags'), which is enough to distinguish it from siblings like list_x402_facilitators. It does not explicitly name an alternative, keeping it at 4 rather than 5.

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 offers a when-to-use clause ('finding available cp0x x402 resources or filtering them by tag'), but this largely paraphrases the purpose. No alternatives or exclusions are named despite a related sibling (list_x402_facilitators) existing.

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