list_api_resources

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

Annotations already declare readOnlyHint=true and openWorldHint=false, covering the read-Only and closed-world behavior. The description adds that CRDs are included and only queryable resources are returned, but it does not disclose response format, pagination, or whether it returns all API versions. No contradiction with annotations.

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?

A single sentence with no filler and the key phrase 'Kubernetes API resources' placed up front. It is appropriately brief for a simple discovery tool, though it misses an opportunity to mention filtering or alternatives.

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 large sibling set and absence of an output schema, the description leaves selection criteria unaddressed and does not clarify that the result is a list of resource types. It is minimally viable but incomplete for reliable tool choice.

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 schema has three parameters (cluster, kind, api_version) with no descriptions. The tool description does not explain how these parameters filter the discovery, whether kind or api_version narrow the result set, or what formats are accepted. Parameter names are somewhat self-explanatory, but the description adds no parameter-level meaning.

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 states a specific verb ('Discover') and a resource ('Kubernetes API resources, including CRDs'), which makes the core purpose clear: enumerate queryable resource types rather than actual resource instances. The reference to CRDs helps distinguish it from tools that list concrete resources, though it could more explicitly say it returns API resource types.

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 when-to-use or alternative guidance is provided. With many sibling list_* tools such as list_crds and list_resources, the description does not tell an agent when to select this tool over them. The usage context is only implied by the phrase 'that can be queried.'

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