delete_region

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

With no annotations, the description must disclose behavioral traits such as destructiveness, undoability, or side effects on project items. It simply states 'Delete a region' without addressing what happens to items within the region or whether the operation is destructive in a particular way. This is a minimal statement of behavior.

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, direct sentence that is easy to parse and front-loads the primary verb. It is concise, though it sacrifices detail that might be expected for completeness.

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 the tool has an output schema but no parameter descriptions, the description is incomplete for an agent to use correctly—it doesn't explain how to obtain a valid region_index or any side effects. For a one-parameter tool, the parameter semantics gap is significant.

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 schema has no descriptions (0% coverage), and the description does not explain what 'region_index' refers to (e.g., zero-based vs one-based, or that it indexes into the region list). The parameter name is somewhat suggestive but lacks the necessary context for correct invocation.

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 the specific verb 'delete' and clearly identifies the resource ('a region') and the scope ('from the project'). This distinguishes it from sibling tools like create_region or delete_marker.

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 over alternatives, nor any prerequisites. For instance, it doesn't mention that the region must exist or that region indices come from get_region_list. The sibling tools imply context but are not referenced.

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