kubectl_apply

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

The description does not disclose traits beyond the 'destructiveHint: true' annotation. It does not explain that 'apply' can create or modify resources, or that it may cause resource deletion if omitted from the manifest.

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 of 9 words, highly concise with no wasted information.

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?

With 6 parameters, no output schema, and a complex operation, the description is insufficient. It lacks details on return values, prerequisites, error handling, and the distinction between manifest and filename usage.

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%, so baseline is 3. The description adds no meaning beyond the schema; it only mentions 'from a string or file' without detailing parameter usage.

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 the action (Apply) and resource (Kubernetes YAML manifest), with source options (string or file). It distinguishes from siblings like 'kubectl_create' by implying a declarative operation, but does not explicitly contrast.

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 use when applying manifests, but provides no guidance on when to use over siblings or when not to. No alternatives or exclusio ns are mentioned.

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