run_kubectl

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

With no annotations, the description carries full burden. It discloses that write operations are recorded in audit log and warns against destructive commands. However, it doesn't mention potential side effects or failure behavior, which would be useful for a tool that can execute arbitrary commands.

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?

Concise and well-structured: purpose, usage guidelines, suitable/avoid commands, audit info, then parameter descriptions. Every sentence adds value without redundancy.

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 tool with 3 parameters, no output schema, and no annotations, the description is highly complete: covers purpose, usage guidelines, behavioral traits, and parameter semantics. Only minor gap is lack of output return format, but that's acceptable for a command execution tool.

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%, so description must explain all parameters. It does so thoroughly: cluster_name target cluster, command as list without 'kubectl' prefix with example, gateway_id optional with guidance on when to omit/provide. Adds meaning beyond 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?

Clearly states it executes kubectl commands on a cluster. Distinguishes from siblings by specifying that it should only be used for operations not covered by dedicated tools, and lists suitable commands (get, describe, logs) as examples.

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?

Explicitly states when to use (operations not covered by dedicated tools) and when not to use (destructive commands). Lists alternatives: scale_deployment, deploy_model, helm_upgrade, helm_uninstall. Also mentions audit logging for write operations.

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