mgmt_cloud_export_remove

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

No annotations are provided, so the description carries the full burden. It identifies a mutating operation but does not disclose whether the action is irreversible, whether special permissions are required, or what the success/failure response looks like. The name says 'remove' while the description says 'disable', leaving ambiguity about the exact side effect.

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 very short and the core action is stated directly. The prefixed documentation URL is not helpful for tool invocation but does not add meaningful verbosity.

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?

For a simple operation with only two required parameters and full schema descriptions, this is adequately scoped for basic invocation. However, with no annotations and no output schema, a note about response format or destructive side effects would make it more complete.

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 already describes all three parameters with 100% coverage, so the baseline is 3. The description adds general resource context but no additional parameter-specific meaning beyond what the schema provides.

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 states a specific action, 'Disable', on a specific resource, 'cloud export on counter'. It clearly distinguishes itself from the only closely related sibling, mgmt_cloud_exports_list, which is a list operation.

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?

Usage context is implied: the agent should call this tool when it needs to disable or remove a cloud export from a counter. However, there is no explicit guidance about prerequisites, when not to use it, or alternatives.

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