check_persistent_volume_capacity

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 effectively describes the tool's function (monitoring PVC capacity) and criticality (preventing crashes/data loss), and mentions that it returns a formatted report with warnings. However, it lacks details on permissions needed, rate limits, whether it's read-only or has side effects, or how the warnings are formatted.

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 well-structured and front-loaded with the core purpose, followed by critical context, parameter explanations, and return details. Every sentence adds value without redundancy, making it efficient and easy to parse for an AI agent.

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 tool's complexity (monitoring critical storage with alerting), no annotations, and an output schema present, the description does a good job covering purpose, usage, and parameters. However, it could be more complete by addressing behavioral aspects like safety (read-only vs. mutating) or error handling, which are important for a tool focused on preventing data loss.

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 schema description coverage is 0%, so the description must compensate. It clearly explains both parameters: 'namespace' (optional filter for PVCs, with 'None' meaning all namespaces) and 'threshold' (alert percentage with default 85%). This adds meaningful context beyond the bare schema, though it doesn't specify units or constraints for 'threshold' beyond the default.

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 the tool's purpose with specific verbs ('monitor', 'checks') and resources ('Persistent Volume Claim (PVC) capacity usage across the cluster'). It explicitly distinguishes this tool from ephemeral storage monitoring, which helps differentiate it from sibling tools like get_cluster_storage_report that might handle different storage types.

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 provides clear context for when to use this tool ('critical for preventing database crashes and data loss due to full disks') and distinguishes it from ephemeral storage. However, it doesn't explicitly mention when NOT to use it or name specific alternatives among the sibling tools, such as get_cluster_storage_report for broader storage analysis.

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