cloud_insts_del

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

The description discloses that the tool deletes an instance and lists parameters like delete_floatings and volumes, hinting at side effects. But it does not explicitly state irreversibility, required permissions, or other behavioral traits, leaving gaps.

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 fairly concise given the tool's complexity, with an Args list and a note block. It is front-loaded with the basic purpose, but could be more streamlined.

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 covers parameters and input resolution well, but lacks information about return values, error handling, or idempotency. Given the high complexity and no output schema, these omissions are notable but not critical.

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 schema description coverage is 0%, but the description provides clear, meaningful explanations for all 11 parameters, including constraints like 'Can't be used with `floatings`' for delete_floatings and resolution logic for project_id and region_id.

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 instance' and lists specific parameters, indicating the action and resource. The tool name 'cloud_insts_del' and its siblings (e.g., cloud_insts_get, cloud_insts_new) help distinguish it from other operations.

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 includes a note on resolving project_id and region_id with fallback behaviors, which implicitly guides usage. However, it does not explicitly state when to use this tool versus alternatives, nor does it mention prerequisites or permissions.

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