resource_delete_instance

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

No annotations are provided, so the description should fully disclose behavior. It only states 'Delete a resource instance' without mentioning whether deletion is permanent, if it requires authentication, or if there are side effects (e.g., cascading deletes). The 'recursive' parameter hints at child deletion but isn't explained in the description.

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 extremely concise, consisting of a single 4-word sentence. It is front-loaded and every word is necessary. No extraneous information.

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 lack of output schema and annotations, the description should cover operation details, return values, and error conditions. It provides none of these. For a delete operation, users need to know if it is destructive, what happens to related resources, and what the response looks like.

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 description coverage is 50% (only 'recursive' has a comment). The description adds no value beyond the schema; it does not explain what 'instance_id' represents or provide context for 'recursive' beyond the schema's own description. For a low-coverage schema, the description should compensate but fails to do so.

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 'Delete a resource instance' clearly states the verb and resource. However, it lacks specificity to differentiate from sibling tools like 'vpc_delete_instance' which also deletes instances, but of a different type. The name itself provides the resource type, so clarity is adequate but not exceptional.

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 vs alternatives (e.g., 'vpc_delete_instance' vs 'resource_delete_instance'). No mention of prerequisites, context, or exclusions. The description is silent on usage conditions.

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