delete_montage_section

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

With no annotations, the description must disclose behavior, but it only says 'Delete a section from a montage.' It doesn't mention permanence, impact on other sections' indices, restrictions (e.g., cannot delete last section), or required permissions. No contradiction exists, but there is minimal behavioral context.

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 extremely concise, with the action stated upfront and parameter details in a clean block. Every sentence earns its place, and there is no redundant wording.

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 two parameters and an output schema, the description is minimally adequate. However, it omits edge cases like deleting the only section or index out-of-bounds behavior, and lacks any consequence information, making it slightly incomplete for safe use.

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 description provides minimal meanings for both parameters: 'asset_path: Unreal asset path' and 'section_index: Index of the section to delete.' Since schema description coverage is 0%, this is the only explanation, but it remains shallow (e.g., no format or 0-based vs 1-based indexing).

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 clearly states the action ('Delete') and the resource ('a section from a montage'). This distinguishes it from sibling tools like add_montage_section or set_section_next.

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 vs alternatives, such as when a section should be removed rather than edited with set_section_time or set_section_next. There is no mention of constraints or prerequisites.

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