kubectl_apply

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

The annotation destructiveHint: true already indicates potential destructive behavior. The description adds no further behavioral details, such as that the tool can create or update resources, or that it requires cluster access. It does not disclose side effects or idempotency.

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 and front-loaded. It avoids unnecessary words, but it may be too brief for a tool with complex behavior.

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?

Given the tool's complexity (applying Kubernetes manifests) and the lack of output schema, the description is insufficient. It does not mention that the operation is applied to a Kubernetes cluster, that it can create/update resources, or what the return value indicates. More context is needed for an AI agent to use 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?

The input schema has 100% coverage with descriptions for all six parameters. The tool description hints at using 'manifest' or 'filename' but does not add significant meaning beyond what the schema already provides. The 'dryRun' and 'force' parameters are well-documented in 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 clearly states that the tool applies a Kubernetes YAML manifest from a string or file. The verb 'apply' and resource 'Kubernetes YAML manifest' are specific. However, among siblings like kubectl_create, it does not differentiate between apply and create, which have different semantics (declarative vs imperative).

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?

No guidance is provided on when to use this tool versus alternatives such as kubectl_create, kubectl_delete, or other siblings. The description simply describes the action without context on appropriate use cases.

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