list_products

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

With no annotations provided, the description carries the full burden. It clearly indicates a read-only listing operation by using 'List' and states the return fields (IDs, names, pricing, availability). However, it does not explicitly state that no side effects occur, mention authentication requirements, or address rate limits or pagination behavior.

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 two sentences, front-loaded with the action and resource, and every sentence adds value. It avoids redundancy and clearly communicates the core purpose and return values without unnecessary detail.

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?

The tool is simple with one optional parameter and no output schema. The description provides return values, which partially compensates for the missing output schema. It does not explicitly state what happens when 'category' is omitted (e.g., returns all products), which is a minor gap for a low-complexity listing tool.

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 documents the single optional 'category' parameter with an enum and a clear description, so schema coverage is 100%. The tool description adds only the product categories 'VPS and blockchain node' and USDC pricing, which aligns with but does not significantly extend 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 uses a specific verb ('List') with a clear resource ('available VPS and blockchain node products') and explicitly notes USDC pricing and returned fields. It clearly distinguishes from siblings like list_instances, which focuses on existing instances, and create_order, which handles ordering.

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 this tool is for browsing the product catalog before ordering, but it does not explicitly state when to use it versus list_instances or create_order. No exclusions or alternative tool names are mentioned, leaving the usage context to be inferred from sibling tool names.

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