put-vhost

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

The description indicates mutation but provides no details on update behavior (merge vs replace), side effects, or authorization needs. Annotations show readOnlyHint=false but openWorldHint=true contradicts the schema's additionalProperties=false, yet the description does not clarify this.

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 only one sentence and lacks necessary detail. While concise, it is under-specified and fails to convey the tool's full purpose.

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?

Given six parameters and no output schema, the description is severely incomplete. It does not explain return values or parameter behavior, leaving the agent with insufficient information to invoke the tool 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?

With 0% schema description coverage, the description adds no information about parameters like name, description, tags, or default_queue_type. The agent cannot infer parameter semantics from the given text.

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 creates or updates a virtual host, using a specific verb and resource. It distinguishes from sibling tools like delete-vhost (destructive) and get-vhost (read-only), though it lacks nuance about idempotency.

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?

No guidance is provided on when to use this tool versus alternatives such as protect-vhost or start-vhost-on-node. Prerequisites like vhost existence for updates are not mentioned.

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