Pod Utilization

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 not disclose default time ranges, pagination/limit behavior, auth or connection requirements, or whether results are cost-limited, leaving the behavioral profile of a 13-parameter query largely unspecified.

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 compact sentences, metrics front-loaded, no filler. Structure is efficient and scannable, though the final 'Same report as...' clause is redundant rather than informative.

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 13-parameter, no-annotation, no-output-schema tool the description is thin: it names the metrics returned but omits default time behavior, connection handling, and result-shape expectations. Adequate to identify the tool, not to call it confidently.

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 92%, so the schema already documents nearly every parameter including time, pod matching, cluster, workload, and namespace. The description's filter list adds little beyond what the schema states, so baseline 3 applies.

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 resource and metrics set: CPU and Memory quota usage, throttled, requests, limits, % of request/limit, unused. Distinguishes scope (Kubernetes Explorer pod quota metrics), though the closing note 'Same report as dynatrace_pod_quota' blurs rather than sharpens sibling differentiation.

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?

Gives filter dimensions (cluster/namespace/workload/pod) but no when-to-use guidance, no prerequisites, and no condition for choosing it over dynatrace_pod_quota despite explicitly stating the two return the same report.

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