delete_region

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

With no annotations, the description carries the full behavioral burden. It states the destructive action 'Delete,' but does not disclose irreversibility, undo behavior, permission requirements, side effects on markers or project state, or error behavior. It provides only minimal transparency 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 front-loaded sentence with no wasted words. It is concise and readable, though its brevity contributes to the gaps in usage and behavior details.

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 destructive one-parameter tool with no annotations, no output schema, and 0% schema description coverage, the description is too thin. It does not explain the return value, error cases, or how to obtain a valid region index, leaving important context to inference.

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%, and the single parameter is only documented by the phrase 'by index.' This adds that region_index is an ordinal identifier, but it does not explain where the index comes from (e.g., get_regions), whether it is zero-based, or what happens if it is invalid.

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 gives a specific verb and resource: deleting a region by index. This clearly separates it from sibling deletion tools such as delete_marker, delete_take, and delete_track. It does not explicitly name an alternative or clarify its role relative to get_regions/add_region, so it stops short of a 5.

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 like delete_marker or delete_take. The agent must infer that it is for removing a region from the project, with no when-to-use or when-not-to-use context.

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