update-pod

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

The description adds value beyond annotations by clarifying that only provided fields change (partial update semantics). Annotations already indicate it's a write operation (readOnlyHint=false) and idempotent, but the description provides important behavioral context about partial updates.

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, clear 17-word sentence with no unnecessary words. All information is relevant and well-structured.

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?

While the description covers purpose and partial update semantics, it lacks information about return values (no output schema) and does not specify which fields are immutable. For a tool with 8 parameters and no output schema, some additional context is missing.

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 coverage is 100% with detailed parameter descriptions. The description groups parameters into categories (name, image, etc.) and emphasizes partial update behavior, adding meaning beyond the schema.

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 explicitly states 'Update a pod's mutable fields' and lists the specific fields, clearly identifying the tool's purpose. It distinguishes this tool from create-pod (creating) and other pod-related 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 usage context by specifying that only provided fields change, suggesting partial updates. However, it does not explicitly state when to use this tool over alternatives like create-pod or delete-pod.

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