get_canonical_manifest

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

No annotations are provided, so the description carries the full burden. It does disclose the data source and that output is verified/unaltered with provenance, but it omits error behavior for unsupported kinds, case sensitivity of the kind value, and any coverage limits of the underlying corpus.

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?

Front-loaded with the purpose, then Args and Returns sections. There is mild redundancy between 'verified, unaltered' and 'Bypasses LLM generative alterations', and the Returns block restates what the output schema already covers.

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 single-parameter lookup with an output schema present, the description covers purpose, source, and argument meaning adequately. The Returns section is redundant given the output schema, and the main gap is guidance on discovering valid kinds via the list_supported_resources sibling.

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 the description must carry the parameter meaning, and it does: 'kind' is defined as the Kubernetes resource kind with four concrete examples (NetworkPolicy, Deployment, ValidatingAdmissionPolicy, ValidatingWebhookConfiguration). It adds no format or case constraints, but the examples are more than the bare schema offers.

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?

States a specific verb and resource ('Retrieves verified, unaltered Kubernetes YAML manifests') and pins the source to official kubernetes.io examples, which separates it from search_k8s_docs. It stops short of naming which sibling to use when a canonical manifest is not available.

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?

The rationale ('Bypasses LLM generative alterations to prevent indentation errors, invalid fields, or deprecated apiVersions') implies the tool should be preferred over generating YAML, which is useful context. However, there is no explicit when-to-use/when-not statement and no reference to list_supported_resources for discovering valid kinds.

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