Opentoonz Delete Workspace

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

No annotations are provided, so the description carries the full burden, and it does: it declares irreversibility, describes the confirmation flow (elicitation prompt when supported, otherwise confirm=true), and explains the destructive consequence of removing scenes and renders. This is rich context beyond the schema.

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?

Front-loads the core action, then the sibling distinction, then the confirmation mechanics. Every sentence earns its place with no 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?

For a destructive mutation tool with no annotations and no output schema, the description covers consequence, irreversibility, alternative routing, and confirmation behavior—everything an agent needs to invoke it safely and correctly.

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 explains the semantics of confirm—that it is the fallback confirmation mechanism when elicitation is unavailable—which is the key parameter behavior not inferable from the boolean type and default. It does not describe workspace's format, but that is a minor omission.

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 (delete) and resource (workspace) with explicit scope: 'including its scenes and renders.' It directly distinguishes itself from the sibling opentoonz_clean by contrasting their behaviors.

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?

Explicitly names the alternative (opentoonz_clean) and states the selection condition: clean empties but keeps usable, this removes entirely. It also explains when confirm is needed vs. elicitation.

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