deploy_pod

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

No annotations are provided, so the description must disclose behavior. It merely says 'deploy,' which implies a mutating action, but offers no details about side effects, failure modes, blocking behavior, or required permissions.

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 a single sentence that is concise but does not add significant value beyond the tool name. It is not verbose, but it is under-specified for a tool with a nested object parameter.

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 deployment action with no annotations, no output schema, and sparse parameter documentation, the description is incomplete. It does not explain required context like cluster existence, pod spec format, or post-deployment validation.

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 sparse (two parameters, no descriptions) and schema coverage is 0%. The description does not mention or explain any parameter roles, leaving the agent without information about what cluster_id or pod_spec mean or how to construct them.

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 ('Deploy'), resource ('a Kubernetes pod'), and destination ('a cluster'). It clearly distinguishes from sibling tools (cluster management, node provisioning) as the only pod-deployment tool.

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?

There is no guidance on when to use this tool vs. alternatives, prerequisites (e.g., cluster must exist), or typical scenarios. The description only states the action without any contextual direction.

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