superset_annotation_layer_delete

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

No annotations are provided, so the description carries full responsibility. It goes beyond a simple statement by adding 'CRITICAL: deletes the layer AND all annotations within it permanently,' highlighting irreversibility and cascading scope. It also flags confirm_delete as required, adding behavioral nuance. It doesn't mention permissions or error cases, but for a delete tool this is substantial coverage.

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 concise and well-structured: a clear action sentence, a critical warning, then bullet-like args. No unnecessary words, and the most important info (permanence) is front-loaded.

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?

Given the tool's destructive nature, the description covers the essential context: what is deleted, permanence, and the required confirmation. Since an output schema exists, return values don't need explanation. It omits details like permissions or side effects on other objects, but for a deletion tool with two parameters, this suffices.

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?

With 0% schema coverage, the description compensates by explaining both parameters: 'annotation_layer_id: Layer ID to delete' and 'confirm_delete: Deletion confirmation (REQUIRED).' It provides essential meaning beyond the bare schema types. The required flag on confirm_delete may conflict with the schema's optional/default behavior, but it adds clarity about the tool's operational requirement.

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 tool's action: 'Delete an annotation layer along with all its annotations.' It specifies the exact resource (annotation layer) and scope (all its annotations), distinguishing it from sibling tools like deleting a single annotation or updating a layer.

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 context: this tool is for deleting an entire annotation layer and its annotations, not individual annotations. It does not explicitly name alternatives or provide when-not-to-use guidance, but the purpose is unambiguous.

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