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

With no annotations, the description carries the behavioral burden. It explicitly states 'Read-only,' which is a key behavioral disclosure, and clarifies ownership scope ('owned by the wallet behind a compute API key'). It does not mention errors or rate limits, but for a simple list operation this is adequate.

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, compact sentence that front-loads the action and resource, immediately lists the output fields, and clearly marks the read-only nature. Zero wasted words.

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 list operation, the description is complete: it states what is listed, the scope, the output fields, and that it is read-only. It does not discuss pagination or error handling, but these are not commonly required for a straightforward read tool, and the parameter is well-defined in the 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 schema fully documents the only parameter (computeApiKey) with a detailed description that includes where to find it and that read scopes are sufficient. The tool description adds nothing beyond what the schema provides, so the baseline score of 3 applies.

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 clearly states 'List the Agent Pods owned by the wallet...' with a specific verb and resource, and enumerates the returned fields (engine, tier, model, status, expiry, AI allowance). It differentiates from siblings like cloud_list_instances and cloud_list_plans by naming the exact resource type (Pods).

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 implicitly tells the agent when to use it (to see the user's pods), but it does not explicitly mention alternatives or exclusions. Given the many sibling tools (cloud_list_instances, cloud_list_plans, etc.), a sentence naming when not to use it would strengthen the guidance, but the scope is otherwise clear.

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