obsbot_tail2_preset_delete

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the post-condition ('verified by the slot disappearing from the list') and that deletion frees the slot, but says nothing about irreversibility, error behavior on an empty/invalid slot, or permissions.

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?

Two short sentences, front-loaded with the action and scope; every clause carries information with no filler.

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, annotation-free tool with no output schema, the description covers the core action and a verification cue but omits the undocumented 'camera' parameter, failure modes, and whether deletion is permanent.

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%, so the description must compensate. It restates the slot range (1–3, redundant with the schema's min/max) but completely ignores the second 'camera' parameter, leaving half the interface undocumented in both schema and prose.

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?

States a specific verb and resource ('Delete a Tail 2 preset slot'), scoped to slots 1–3, so the agent knows exactly what is affected. It does not, however, distinguish itself from the closely named generic sibling obsbot_preset_delete, leaving the model-specific vs generic choice implicit.

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 never states when to use this over obsbot_preset_delete, obsbot_tail2_preset_save, or obsbot_tail2_preset_rename, nor any prerequisite (e.g., slot must already exist). Usage is only implied by the verb.

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