scobees_delete

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

With no annotations provided, the description carries the full behavioral burden. It does disclose the important cascade behavior ("inkl. Unterelementen!") and the confirm requirement, but omits irreversibility, permission requirements, and what happens if the ID is invalid.

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, front-loaded sentence with the verb first and the cascade warning emphasized. It is efficient, though the exclamation mark is informal and the parenthetical could be integrated more cleanly.

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 tool with no annotations and no output schema, the description covers the key cascade risk and confirm requirement. It still leaves out irreversibility, error behavior, and return semantics, which are important for a delete operation, so it is only minimally adequate.

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 50%: confirm is documented in both schema and description, but id has no description in either. The enumeration of deletable entity types indirectly clarifies what id may refer to, providing some value beyond the schema, but not full compensation for the undocumented id parameter.

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 ("Löscht") and enumerates exactly which resource types can be deleted (Aufgabe, Gliederung, Wahlpflichtaufgabe, Lernpfad). It is clearly a delete operation, though it does not explicitly contrast itself with the sibling update/create tools.

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?

Usage is implied by the verb "Löscht" and the prerequisite "Erfordert confirm=true" is stated, which is useful. However, there is no explicit guidance on when to choose this over sibling tools like scobees_update_* or scobees_move, nor any warning about when not to use it.

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