k8s_get_resources

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

No annotations provided, so description carries full burden. It discloses auto-detection of API groups for common kinds and requirement of group/version for custom resources, and that omitting namespace queries all. However, it does not mention safety (likely read-only), pagination, rate limits, or authentication needs.

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?

Three sentences with clear front-loading: first defines purpose, second explains auto-detection, third covers namespace behavior. No wasted words.

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 5 parameters and no output schema, the description covers purpose, kind, group/version for custom resources, and namespace behavior. However, it lacks details on context format, return type (e.g., list of names or full objects), and any limits. Moderately complete but with gaps.

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 0% (no parameter descriptions), so description must compensate. It explains 'kind' as resource type, 'group' and 'version' as needed for custom resources, and 'namespace' optional for all-namespace. It does not detail 'context' but overall adds significant meaning beyond 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 the tool lists Kubernetes resources of a specified kind, with examples like Pod and Deployment. It distinguishes from the singular 'k8s_get_resource' sibling by specifying plural listing.

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?

Clear stating when to use: to list resources by kind. Implicitly excludes getting details or logs by naming siblings. Includes advice on omitting namespace for all-namespace queries, but lacks explicit when-not-to-use or alternatives.

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