apex_delete_region

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is clear. The description adds no extra behavioral context such as irreversibility, cascading effects, or error conditions. It neither contradicts nor enriches the annotation-provided information.

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?

A single sentence of eight words that immediately states the action. No filler or redundancy, perfectly front-loaded and easy to parse.

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 delete operation with full schema coverage and annotations, the description is adequate. It does not explain edge cases or error handling, but the presence of an output schema and annotations reduces the need for the description to cover those aspects. Missing explicit alternatives is a minor gap.

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 coverage is 100% with each parameter described ('Application ID', 'Page ID', 'Exact name of the region to delete'). The description itself adds no additional semantic details beyond the schema, so the baseline of 3 applies.

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 ('Delete') and resource ('a region from an existing app'), clearly distinguishing it from sibling tools like apex_delete_page, apex_delete_item, and apex_delete_button. It is concise and unambiguous about the 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?

No guidance is provided on when to use this tool versus alternatives (e.g., apex_update_region for modifying, apex_add_region for creating). The description does not mention prerequisites or context such as requiring an existing region name or page.

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