create_pod

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

With no annotations provided, the description carries the behavioral burden. It discloses that the pod is persistent, that it includes a Docker container and volume, and that no app files are deployed. It does not mention return values or conflict behavior, but the core side effects are clearly stated.

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 short sentences with no wasted words. The core definition comes first, clarified in parentheses, and the deployment guidance is delivered in the second sentence. Every element earns its place.

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 two-parameter creation tool, the description covers the essential concept, the persistent side effect, and the relationship to deploy_pod. The absence of return-value details is a minor gap, but not enough to block a correct invocation.

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?

Schema description coverage is only 50%, and the description adds no parameter-level meaning. It does not explain how 'preset' affects the pod or clarify 'name' beyond what the schema already provides. The description should compensate for the partially undocumented schema but does not.

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 states a specific verb and resource ('Create a new empty pod') and immediately defines what a pod is in parentheses. It explicitly contrasts with deploy_pod by noting no app files are deployed yet, making it easy for an agent to distinguish the operation.

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 gives direct usage guidance: 'Usually you can skip this and call deploy_pod directly.' This explicitly names the alternative and states when this tool is unnecessary, which is exactly what an agent needs to choose the right sibling.

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