create_namespace

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

The most critical behavioral trait is disclosed: the tool is 'a dry run unless dry_run=False', meaning the default call does not actually create anything — exactly the kind of surprise an agent needs to avoid. It also reveals the dual return contract ({namespace, status, cluster} vs {dry_run, spec}). This adds substantial context beyond annotations, which only state readOnlyHint=false and destructiveHint=false; no contradiction exists.

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?

Three sentences, zero filler: purpose, return contract with the critical default, then sibling routing. The essential safety caveat (dry-run default) is front-loaded in the second sentence rather than buried, and every clause earns its place.

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 correctly carries the return-format burden and covers the full create/update/verify lifecycle. What's missing for an 8-parameter creation operation is an error/null contract (e.g., what happens if creation fails or the namespace exists) and any permission prerequisites, but the fully-documented schema and clear sibling routing make the tool safely callable.

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 100%, and the schema already documents every parameter including the dry_run default of true, sources for cluster_id and storage_policy, and units for limits. The description only restates the dry_run default, adding nothing that meaningfully improves parameter understanding beyond what the schema provides, so the baseline 3 applies.

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 a specific verb and resource ('Create a vSphere Namespace on a Supervisor Cluster') and the '[WRITE]' tag marks it as a mutation, distinguishing it from the many read-only siblings. It explicitly names update_namespace as the tool it should not be confused with, so an agent can disambiguate immediately.

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?

Gives explicit routing: 'Use update_namespace instead when it already exists' names the alternative and the exact condition that selects it. It also prescribes a follow-up step ('confirm with get_namespace afterwards'), which is actionable usage guidance beyond mere capability description.

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