delete-vhost-limit

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

The description indicates a destructive action ('Delete'), consistent with the annotation 'readOnlyHint: false'. However, it does not disclose any additional behavioral traits such as irreversibility, side effects, or error conditions (e.g., behavior when limit does not exist). The description adds minimal value beyond the annotation.

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 a single sentence, which is concise but at the expense of necessary detail. It earns its place but could be improved by adding parameter explanations or usage hints without becoming verbose.

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?

The description is too brief given the lack of output schema, parameter explanations, and sibling tool differentiation. It does not provide sufficient context for an agent to understand the tool's purpose fully, such as what constitutes a 'vhost limit' or the effect of deletion.

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 must compensate by explaining the parameters. However, it provides no information about the 'vhost' and 'name' parameters, leaving the agent to guess their meaning and format. This is a critical gap for correct invocation.

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 action 'Delete' and the resource 'vhost limit', distinguishing it from sibling tools like 'delete-user-limit' by specifying the resource type. However, it does not explain what a vhost limit is, which could be ambiguous without domain knowledge.

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?

The description provides no guidance on when to use this tool versus alternatives. There is no mention of prerequisites, when not to use it, or differentiation from similar tools like 'put-vhost-limit' or 'delete-user-limit'. The agent is left to infer usage context from the tool name alone.

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