top-pods

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'resource usage' but fails to specify what metrics are shown, how data is formatted, whether it's real-time or historical, or any constraints like permissions or rate limits. This leaves significant gaps for a tool that likely interacts with system resources.

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, efficient sentence with no wasted words. It's front-loaded with the core purpose, making it easy to scan and understand quickly, which is ideal for conciseness.

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 complexity of monitoring resource usage, no annotations, and no output schema, the description is insufficient. It doesn't explain what 'resource usage' includes, the output format, or behavioral aspects like data freshness or limitations, leaving the agent with inadequate information for effective use.

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 1 parameter with 100% description coverage, so the description doesn't need to add parameter details. It correctly avoids redundancy, and with 0 parameters requiring explanation from the description, it meets the baseline for adequate coverage without unnecessary repetition.

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 'Show resource usage for pods' clearly states the verb ('show') and resource ('pods'), but it's vague about what 'resource usage' specifically entails (e.g., CPU, memory, or other metrics). It doesn't differentiate from siblings like 'get-pod-metrics' or 'top-nodes', leaving ambiguity in scope.

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 guidance is provided on when to use this tool versus alternatives such as 'get-pod-metrics' or 'analyze-resource-usage'. The description lacks context about prerequisites, exclusions, or typical use cases, offering no help in tool selection.

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