list-fleet-instrumented-pods

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

With no annotations, the description must carry the full burden of behavioral disclosure. It only states that the tool 'list[s] pods', implying a read-only operation, but does not clarify authorization needs, pagination, scoping (e.g., namespaces), or output format. This leaves the agent without critical safety and behavioral cues.

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, well-structured sentence that immediately communicates the tool's purpose. No superfluous words or unnecessary details are present.

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 simplicity (one parameter, no output schema), the description should explain what SSI means and what the returned data represents (e.g., pod names, statuses). The lack of such context and absence of usage guidance leaves the agent underinformed.

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% parameter description coverage, providing a baseline of 3. The description adds minimal extra meaning beyond the schema; it restates the cluster context without elaborating on SSI specifics or parameter constraints.

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 uses a specific verb 'List' and a clearly defined resource 'pods targeted for Single Step Instrumentation (SSI)', which is distinct from sibling list tools that cover other entities like agents, clusters, or deployments. The acronym SSI is expanded in parentheses, aiding understanding.

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 explicit guidance is provided on when to use this tool versus alternative list tools (e.g., list-fleet-agents, list-containers). The description does not mention prerequisites, exclusions, or context such as cluster management requirements.

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