list_namespace_storage_usage

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

Describes return envelope structure, mentions that every PVC comes back in one call and truncated is always false. Adds context beyond annotations (readOnlyHint, etc.) without contradiction.

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?

Well-structured with clear sections, front-loaded with purpose. Slightly verbose with deprecated alias details but all information is useful.

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?

Covers prerequisite, alternative tool, return envelope, parameter docs, and deprecated aliases. No output schema, but description provides thorough coverage.

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?

Description provides explicit Arg definitions for namespace and target, adding meaning beyond the input schema which only has titles and types. Schema coverage is 0%, but description compensates fully.

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?

Explicitly states it lists PersistentVolumeClaims and storage usage inside a vSphere Namespace via the Supervisor K8s API. Distinguishes from sibling list_supervisor_storage_policies by specifying policy-level vs PVC-level information.

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?

Clearly instructs to run list_namespaces first for the namespace and recommends list_supervisor_storage_policies for policy-level needs. Also explains deprecated aliases and that truncated is always false.

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