List services

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

With no annotations provided, the description carries the full burden. It accurately describes a read-like listing operation with live rates and no API key requirement. While it doesn't explicitly state 'read-only', the context implies no destructive behavior. The description adds useful behavioral context beyond the empty schema.

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, no wasted words. The first sentence states the purpose and key data points; the second provides usage context. Information is front-loaded and efficiently structured.

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 zero parameters, no output schema, and the presence of sibling tools like 'create_order' and 'get_balance,' the description is complete. It explains the tool's role in the workflow (discovery before ordering) and all necessary details for an AI agent to use it correctly.

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?

There are zero parameters, and schema coverage is 100% trivially. The description adds meaning by detailing what the output contains (rates per 1000, min/max, link requirement), compensating for the lack of a structured output schema. It clarifies the semantic value of the tool beyond the empty input schema.

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') and resource ('Stars Cash Flow service catalog'), and explicitly mentions the key attributes (live USD rates, min/max quantity, link requirement). It clearly distinguishes itself from sibling tools like 'create_order' and 'get_balance' by positioning itself as a discovery tool for pricing orders.

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 explicitly says 'Use this to discover service IDs and price an order before calling create_order,' providing clear when-to-use guidance. It also states 'No API key required,' a prerequisite. It does not mention when not to use it or alternatives, but given zero parameters and a straightforward purpose, this is adequate.

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