list_namespace_storage_usage

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true. The description adds that it lists PVCs and storage usage, but does not disclose additional behaviors such as pagination or authorization needs. It does not contradict annotations.

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 short and front-loaded with the '[READ]' tag. It uses two sentences plus a parameter list, with no unnecessary words. Every sentence adds value.

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 simple list tool with two parameters and no output schema, the description covers what the tool does and its parameters. It could clarify that target is optional, but the schema defaults cover that. Annotations are rich, so completeness is high.

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 provides brief meanings for each parameter: 'vSphere Namespace name' for namespace and 'vCenter target name' for target. This adds basic context beyond the schema types, but the descriptions are minimal.

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 lists PVCs and storage usage for a vSphere Namespace, with the verb 'List' and specific resource. It distinguishes from sibling tools like list_namespaces or list_supervisor_storage_policies.

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 indicates it is a READ operation but provides no explicit guidance on when to use this tool versus alternatives, nor any exclusions. The context is clear for a storage usage listing but lacks comparative hints.

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