timeweb_delete_vpc

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

With no annotations, the description carries the burden. It discloses that deletion is permanent and that the VPC must be detached from services first, providing critical behavioral context. It doesn't detail error behavior or side effects beyond that, but the essential risks are covered.

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 with no redundant words, front-loading the action verb. It earns it place by adding the permanence and dependency constraints.

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 straightforward delete operation with two schema-documented parameters, this description covers the key facts: action, permanence, and precondition. It doesn't explain return values, but no output schema exists. Overall, it is sufficient for an agent to invoke it 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 input schema already describes both parameters (vpc_id, format) with 100% coverage, so the description doesn't add extra parameter meaning. The baseline of 3 applies as the schema handles the semantic load. No further elaboration is necessary.

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 uses a specific verb 'Delete' and resource 'VPC', with 'permanently' clarifying the scope. It clearly distinguishes from sibling delete tools for other resources and from VPC-related tools like get/create/update.

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 states a clear condition for use: the VPC must not have any attached services. While it doesn't explicitly name alternative tools, the delete operation's context is obvious given the resource type. It could mention what to do if services are attached, but the precondition serves as a guide.

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