get_pod_metrics

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

With no annotations, the description must disclose behavioral details, but only mentions that pod_name can be a regex pattern and lists metric types. It does not state whether data is live or historical, whether regex can match multiple pods, what units/format are returned, or any operational caveats.

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 compact and front-loaded with the core purpose, followed by a clearly structured Args block. No redundant or vague sentences are present; every line adds useful information.

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?

The tool appears simple and has an output schema, so some missing return details are acceptable. However, the description lacks any context on time range, meaning of regex results, or distinctions from adjacent monitoring tools. It is minimally sufficient but not fully self-contained.

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%, but the description compensates by explaining each parameter: pod_name accepts a name or regex, namespace is a Kubernetes namespace, and metric_type enumerates five valid values. This goes well beyond the bare schema titles and defaults.

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?

Description states a specific verb and resource: 'Get metrics for a Kubernetes pod' with the metric categories CPU, memory, restarts, and network in parentheses. This is clear and distinguishable from siblings like query_pod_logs, though it does not explicitly name an alternative for cases like custom Prometheus queries.

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 on when to use this tool versus siblings like query_prometheus or query_k8s_events. The description only defines what the tool does, not the conditions that select it or when not to use it.

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