runpod_list_pods

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

Explicitly marks tool as 'Read-only'. No annotations exist, so description carries full burden. Discloses that it only lists and does not mutate state. Could mention that no changes are made, but 'Read-only' suffices.

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 plus a single-word phrase. No redundancy. Essential information front-loaded. Every sentence adds value.

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, parameterless list tool with no output schema, the description is fully complete: purpose, usage, output fields, error handling, and safety. No missing information.

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?

No parameters, schema coverage 100% (vacuous). Description adds value by listing the fields returned (id, name, status, GPU, cost), which the schema does not specify. Baseline 4 for 0 parameters.

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?

Clear verb 'List' and resource 'pods'. Specific fields enumerated (id, name, status, GPU, cost). Distinguishes from sibling pod tools by being the 'list all' variant.

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?

Explicitly states when to use (no pod ID given, need to find one) and what to do if no pods (tell user to create one, share deploy link). Provides clear decision context.

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