list_namespaces

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

The description discloses the response envelope, item shape, status semantics, and pagination behavior ('one call returns them all, so truncated is always false'). This adds substantial value beyond the annotations, which already declare read-only, idempotent, non-destructive behavior.

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 and [READ] marker. Every sentence carries useful information: what is listed, what the return envelope contains, and how to proceed through sibling tools. No filler or repetition.

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 one optional parameter, this is complete. The description covers the response format, status values, pagination behavior, and provides navigation to relevant sibling tools, so an agent has everything needed to invoke it correctly.

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 coverage is 100%, so the single optional target parameter is already well documented in the schema. The description does not add further parameter details, but no compensation is needed given the high schema coverage.

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 names a specific verb and resource: 'List all vSphere Namespaces on the target vCenter with their status.' It also distinguishes itself from related siblings like get_namespace and list_tkc_clusters by noting that it returns the full set of namespaces and is the intended entry point.

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?

Explicit guidance is provided: 'Start here, then call get_namespace for detail, list_tkc_clusters for what runs inside, or update_namespace / delete_namespace to change one.' This tells an agent exactly when to use this tool and what to use next based on intent.

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