list_namespaces

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

Beyond the annotations (readOnlyHint, idempotentHint), the description discloses the return envelope structure, status value meanings, and pagination behavior ('one call returns them all, so truncated is always false'). This is useful behavioral context that annotations alone do not convey.

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-organized: purpose, return semantics, usage guidance, and parameter note. Each sentence adds value, and the [READ] tag front-loads the safety profile, though it is slightly longer than strictly necessary.

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?

With no output schema, the description compensates by detailing the list envelope and status semantics, covers the single parameter, and provides navigation guidance. It fully equips the agent to use the tool correctly and safely.

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 only parameter, target, is explained as 'vCenter in config.yaml; omit for the default', adding meaning absent from the schema, which has no descriptions for properties. This compensates for the 0% schema description 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 opens with '[READ] List all vSphere Namespaces on the target vCenter with their status', a specific verb+resource+scope. It further distinguishes itself from siblings by directing to get_namespace for detail, list_tkc_clusters for what runs inside, and update/delete_namespace for modifications.

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?

It explicitly positions the tool as the entry point: 'Start here' and names alternatives for next steps, making the usage context unmistakable. This clearly answers when to use this tool versus siblings.

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