cdp_deactivate_provision_instance

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action is a DELETE operation, implying a destructive mutation, but doesn't specify effects (e.g., data loss, state changes), permissions required, or error handling. This is insufficient for a mutation tool.

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, efficient sentence with no wasted words, front-loading the core action. It's appropriately sized for the tool's complexity.

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 a destructive mutation tool with 2 parameters (0% schema coverage), no annotations, and an output schema (which might cover return values), the description is incomplete. It lacks parameter explanations, behavioral details, and usage context, making it inadequate for safe and correct tool invocation.

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 0%, so the schema provides no parameter details. The description mentions no parameters, failing to explain what 'instance_id' or 'tenant_id' represent, their formats, or how they affect the operation. It doesn't compensate for the low coverage.

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 ('Deactivate') and resource ('a provisioned instance'), making the purpose specific and understandable. It distinguishes from siblings like 'cdp_deprovision_instance' by focusing on deactivation rather than full deprovisioning, though it doesn't explicitly compare them.

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 provides no guidance on when to use this tool versus alternatives like 'cdp_deprovision_instance' or 'cdp_reactivate_provision_instance', nor does it mention prerequisites or context for deactivation. It lacks explicit usage instructions.

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