copy_pod_files

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

With no annotations provided, the description carries the full burden and covers it well: it explains direction-specific behavior, encoding for binary files, how local_path changes the flow, and return values. It also notes that to_pod file writes are confirmed and from_pod returns content or a saved path.

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 front-loaded with a one-line purpose, then uses a structured Args list and a Returns note. Every sentence adds value, and the information density is high without being verbose.

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 10-parameter, two-direction file-copy tool with no output schema, the description covers all essential behavior: parameter meanings, direction logic, encoding, defaults, container selection, and return values. It is self-sufficient for an agent to invoke it correctly.

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 0%, but the description compensates by explaining every parameter, including conditional requirements (content is required when local_path is not specified), defaults (namespace=default, encoding=text), and formats (pod_paths as JSON array or single path). This goes far beyond the raw 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 states a specific action: copy files between a Pod and the MCP client, and the Args section defines both directions (from_pod/to_pod). This clearly distinguishes it from siblings that inspect logs, execute commands, or manage clusters.

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 Args give explicit usage conditions: direction values, when content is required, local_path alternatives, namespace default, multi-container requirement, and kubeconfig fallback logic. It does not explicitly mention when to avoid this tool in favor of a sibling, but the context is otherwise clear.

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