ibmcloud_resource_service_instance_delete

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

With no annotations, the description must disclose behavioral traits itself. It only says 'Delete a service instance' without noting permanence, cascading effects, or any cautionary details. For a destructive operation, this is a significant transparency gap.

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, concise sentence that front-loads the action and resource. There is no filler or redundancy, making it highly efficient and appropriately sized for a simple delete operation.

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?

Even though the parameter schema is comprehensive, the description lacks essential behavioral context for a destructive tool. It does not explain return values, prerequisites, or any warnings, leaving the agent without enough information to safely invoke the operation.

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 fully describes both parameters (name and force) with clear descriptions, so the description does not need to add parameter semantics. The schema coverage is 100%, which meets the baseline for a score of 3.

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 ('a service instance'), which is a specific verb+resource pairing. It does not explicitly distinguish from siblings like create or update, but the name and verb make it unambiguous enough. However, it lacks extra context that would earn a 5.

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 gives no guidance on when to use this tool versus alternatives, no mention of prerequisites, force flag behavior, or potential warnings. It is a bare imperative without any usage context, earning a low score.

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