delete-vhost

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

Annotations already indicate this is a write/destructive operation (readOnlyHint=false). Description adds no additional behavioral insight beyond the verb 'Delete', such as side effects, idempotency, or error states.

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?

Single sentence with zero fluff. Efficiently conveys the core action without redundancy.

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 delete operation with one parameter and no output schema, the description is too minimal. It omits crucial context like success/failure indicators, whether the operation is synchronous, or what happens to dependent resources.

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 0% for the only parameter 'name'. Description does not explain what the name represents (e.g., vhost identifier) or provide any format hints, leaving the agent with only the schema's type constraint.

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?

Description is direct and specific: 'Delete a virtual host'. Clearly states the action and resource, and distinguishes from sibling delete tools targeting other resources (e.g., delete-exchange, delete-queue).

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 on when to use this tool versus alternatives. Lacks context such as prerequisites (e.g., vhost must exist, impacts on bindings) or conditions under which deletion is allowed.

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