Server Quality Checklist

Tool Scores

• kube_pod_execA
  4/5.0
  Behavior4/5

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

  Annotations already disclose mutation (readOnlyHint=false) and destructiveness (destructiveHint=true). The description adds meaningful behavioral context by stating that stdout/stderr are captured and returned only when the command completes, which implies blocking behavior and output aggregation. This goes beyond the structured annotations without contradicting them.

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness5/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  The description is two concise sentences that front-load the core action ('Execute a command in a container of a pod') and immediately add the key behavioral detail about output capture. Every word earns its place, with no redundancy or fluff.

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness4/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  Given the tool's complexity (10 parameters, a oneOf construct, output schema, and annotations covering safety), the description covers the essential context: what it does and how it returns output. It could add more usage differentiation vs. run_code, but the clear title and schema make it adequate for an annotated tool.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters3/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  The input schema has 100% description coverage, detailing all 10 parameters including the oneOf alternatives for args/argv/command. The description itself contributes no parameter-specific information, but the schema fully explains semantics, so the baseline score of 3 is appropriate.

  Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

  Purpose5/5

  Does the description clearly state what the tool does and how it differs from similar tools?

  The description explicitly states the tool executes a command in a pod container via the Kubernetes API, with the phrase 'no kubectl' distinguishing it from a kubectl-based approach. It clearly identifies the verb (execute), resource (pod container), and method, and further notes output capture, providing a complete purpose.

  Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

  Usage Guidelines3/5

  Does the description explain when to use this tool, when not to, or what alternatives exist?

  The description implies usage for Kubernetes pod execution via the Kubernetes API, but it does not explicitly compare to the sibling tool run_code or offer when/when-not guidance. The 'no kubectl' designation provides a minor usage hint but is not a clear alternative comparison.

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

• run_codeA
  4.2/5.0
  Behavior4/5

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

  The description adds valuable behavioral context beyond the annotations, such as 'bounded' execution, top-level await, 'progressively discovered' capabilities, and the ability to inspect tools.disabled() for policy denials. It does not contradict the readOnly, non-destructive, idempotent hints, and it enhances understanding of the sandboxed runtime.

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness5/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  The description is three sentences, front-loaded with the core purpose in the first sentence. Every sentence earns its place: the second explains how to interact with the environment, and the third points to additional documentation. There is no redundancy or filler.

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness4/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  Given the tool's complexity (arbitrary code execution in Kubernetes) and the presence of an output schema, the description is quite complete. It covers the execution model, discovery mechanism, policy-denial introspection, and where to find full docs. It does not explicitly address when to prefer this over kube_pod_exec, but the different purposes are implicit. Overall, it is sufficient for an agent to invoke the tool correctly.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters3/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  Schema coverage is 100% for the two parameters, so the baseline is 3. The description adds minor clarification (e.g., 'Return a value from the script' implies the code parameter should produce a return value), but it largely repeats what the schema already states (TypeScript code, top-level await support). It does not add substantial parameter-level semantics beyond the schema.

  Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

  Purpose5/5

  Does the description clearly state what the tool does and how it differs from similar tools?

  The description clearly states the tool executes bounded TypeScript with top-level await against Kubernetes capabilities, using a specific verb ('Execute') and resource ('bounded TypeScript'). It distinguishes itself from the sibling tool kube_pod_exec by focusing on analysis code rather than command execution in pods.

  Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

  Usage Guidelines4/5

  Does the description explain when to use this tool, when not to, or what alternatives exist?

  The description provides explicit guidance on how to use the tool: use tools.list(), tools.search(), tools.help(), and typed namespaces, and inspect tools.disabled() for policy denials. It implies this is the tool for exploring and analyzing Kubernetes capabilities, but does not explicitly compare it to the sibling or state when not to use it, so it falls short of a full when/when-not guideline.

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