Delete Vultr instance

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

Annotations already indicate destructiveHint=true, so the description adds procedural context beyond annotations: that the agent should fetch the instance first, check its label, and require exact confirmation. This is valuable additional transparency.

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 clear sentence with no wasted words. It efficiently conveys the purpose and required verification steps.

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 the tool's destructive nature (3 required params, no output schema), the description adequately explains the verification workflow. It does not mention return values or prerequisites like authentication, but the step guidance is sufficient for an agent to understand the expected usage.

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 low (33%), and the description does not individually describe each parameter. However, it provides context (e.g., label is checked, confirm must be exact) that adds meaning beyond the schema. More explicit parameter descriptions would improve this score.

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 'Delete a Vultr instance', specifying the verb and resource, and distinguishes it from siblings like reboot_instance and create_instance by mentioning the prerequisite steps of fetching, label checking, and exact confirmation.

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 implies when to use the tool (after fetching, checking label, and having exact confirmation) but does not explicitly state when not to use it or mention alternative tools like reboot_instance. The step-by-step guidance is helpful.

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