ubos_store_products

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

With no annotations, the description carries full behavioral burden. 'List' clearly signals a read-only operation and 'any agent can pay-per-call' conveys access rules, but the description does not mention whether listing itself costs USDC, what the response format looks like, or whether pagination or filtering 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, well-front-loaded sentence states the action, resource, payment model, and two illustrative examples. Every element earns its place, and there is 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 parameterless list tool, the description gives the core purpose, examples, and pricing context. It lacks an explicit statement of the return format, but the verb 'List' and the examples make the expected output reasonably clear even without 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 has zero parameters, so there is nothing for the description to clarify. The baseline for zero-parameter tools is 4, and the description adds no unnecessary parameter details.

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 opens with a specific verb ('List') and a clear resource ('UBOS x402 metered tools'), then gives concrete examples (governor, hotvessel) with prices. This makes the tool's purpose unmistakable and distinguishes it from siblings like ubos_store_call or kinematic_pricing, which are about calling or pricing rather than cataloguing.

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 is for discovering available metered tools and their costs before purchasing calls, but it never explicitly states when to use it versus alternatives such as kinematic_pricing or ubos_store_call. There is clear context but no exclusionary guidance.

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