delete_alias

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

There are no annotations, so the description must carry the behavioral disclosure burden. It communicates the destructive 'delete' action but does not mention whether deletion is permanent, whether related scene data is affected, or whether any permission/state requirements exist. This is thin 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?

A single sentence, no filler, and immediately actionable. It uses the remaining tokens for the only relevant bit of context: that an alias is a scene exception.

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?

The tool is simple, has one parameter, and an output schema exists, so no return-value documentation is needed. However, with no annotations and no behavioral context, the description still leaves a destructive action without side-effect or irreversibility caveats. Acceptable but minimal.

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 already describes the only parameter (alias_id) at 100% coverage, so the description does not need to add much. It also does not elaborate on how alias_id should be obtained or what constitutes a valid ID; baseline for high schema coverage is appropriate.

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 concrete verb ('Delete') and a specific resource ('alias'), and clarifies that an alias is a scene exception. That makes its purpose unambiguous and distinguishes it from siblings like create_alias and get_aliases without needing more detail.

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 explicit guidance about when to prefer this tool over alternatives or when not to use it. The delete semantics imply the intended use, but the description does not offer any comparison or exclusions beyond the operation itself.

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