ue_sequence_remove

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

With no annotations, the description carries the burden of behavioral disclosure. It reveals a non-obvious consequence: if neither `track` nor `track_type` is provided, the whole binding is removed. This is crucial destructive behavior that goes beyond the schema's default null values.

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, focused sentence that front-loads the action ('Toglie una track...') and then clarifies the alternative behavior. No unnecessary words or redundancy.

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?

Despite no annotations or output schema, the description adequately covers the primary decision logic (track vs. whole binding removal). It omits details like error handling or return values, but the core usage is sufficiently clear for an agent.

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 adds meaning to `track` and `track_type` by explaining their role in the removal logic, which is valuable given 0% schema description coverage. However, it does not elaborate on `sequence_path` or `binding`, though their purpose is partially inferable from their names.

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 ('remove') and clearly specifies the resource ('track from a binding' or 'entire binding'), distinguishing between two operation modes. It differentiates from sibling tools like `ue_sequence_add_track` and `ue_sequence_info` by its clear removal intent.

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 clear usage context by explaining the two scenarios: specifying either `track` or `track_type` removes a track, while omitting both removes the entire binding. It does not explicitly name alternative tools, but the guidance on parameter selection effectively directs usage.

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