Cancel App Recovery

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

With no annotations, the description carries the burden of behavioral disclosure. It does disclose that the operation is unavailable in read-only mode, which is useful, but it does not explain side effects, reversibility, or what happens if the recovery action is already deployed. This is sufficient but minimal.

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 two short, information-dense sentences. The core action is front-loaded, and the read-only restriction earns its place by preventing incorrect invocation. No filler or redundancy.

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 two-parameter cancel operation with an output schema, the description is minimally complete. However, it lacks lifecycle context such as whether cancellation applies only to pending recoveries and how this relates to related tools like deploy_app_recovery or add_app_recovery_targeting.

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 covers both required parameters with clear descriptions ('App package name' and 'App recovery action ID'), so schema coverage is 100%. The description adds no additional parameter-level meaning beyond what the schema already provides, matching the baseline.

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 uses a specific verb, 'Cancel', with a clear resource, 'app recovery action'. It is distinguishable from sibling operations like create_app_recovery, deploy_app_recovery, and list_app_recoveries, though it does not explicitly name 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?

There is no guidance on when to use this tool versus alternatives, and no mention of prerequisites or lifecycle context. The only added note, 'Disabled in read-only mode', is a constraint rather than a usage-selection rule.

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