List DIEM Agent Workers

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

No annotations are provided, so the description carries the behavioral burden. It explicitly states the tool is free, which is useful context, and 'List' implies a read-only operation. However, it does not discuss authentication, rate limits, or potential side effects, though for a simple listing these are less critical.

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 short sentences with no wasted words. It front-loads the core purpose and adds a valuable cost-related note ('This tool is free') without redundancy.

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 there is no output schema and no annotations, the description covers the main return categories (prices, schemas, limits, endpoints) and cost behavior. However, terms like 'x402-paid' and 'bounded' are undefined, and the relationship to quote/prepare siblings is not explained, leaving minor 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?

The input schema is empty (0 parameters), so the baseline is 4 and there are no parameter semantics to clarify. The description instead enumerates the output content (exact USDC prices, schemas, limits, endpoints), which helps the agent understand what the listing will provide.

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 ('bounded x402-paid workers') and the exact data returned (USDC prices, schemas, limits, endpoints). This clearly distinguishes it from siblings like quote_diem_worker and prepare_diem_worker_call, which are not list operations.

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 is a free catalog/inspection tool, but it does not explicitly state when to use it versus the sibling quote/prepare tools. The phrase 'This tool is free' hints that it is a safe way to browse before committing, but no explicit when-to-use or exclusions are provided.

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