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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the agent knows it's safe. The description adds that it's 'similar to kubectl describe', which conveys that output is detailed and human-oriented. It does not mention potential large output size or pagination, but given annotations cover the safety profile, this is adequate and adds useful context beyond 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?

Two sentences, immediately states the core purpose and an analogy. No fluff. Perfectly sized for the tool.

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 an output schema exists and annotations indicate a safe read, the description is complete enough for a describe-like operation. It could mention what 'details' includes, but the kubectl describe comparison covers that. For a tool with good structured data, this is sufficient.

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 100%, so the input schema already documents all five parameters with descriptions. The description itself adds no extra parameter detail. Baseline 3 is appropriate since schema does the heavy lifting; no additional semantics needed.

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 it 'shows the details of a specific Kubernetes resource' and compares to 'kubectl describe', which is a specific verb+resource. It distinguishes from siblings like get_k8s_resource (which likely returns a summary) and list_k8s_events, but doesn't explicitly contrast with them, so not a 5.

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 description implies usage: use when you need detailed information about a resource, similar to kubectl describe. It does not explicitly state when not to use it or mention alternatives, but the analogy to 'kubectl describe' provides context that it's for detailed inspection rather than listing. It lacks explicit exclusions or guidance about when to use get_k8s_resource or list_k8s_api_resources instead.

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