delete_workspace

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It explicitly states the action is irreversible and deletes all documents and data associated with the workspace, and mentions the return type (Dict with status and message). This provides good transparency for a destructive operation.

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 with a clear main sentence followed by a warning in a separate paragraph. It contains no unnecessary words and is front-loaded with the key action. However, it could be slightly more comprehensive without becoming verbose.

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?

The description is adequate given the tool has one parameter and an output schema (which covers return values). However, it lacks guidance on prerequisites (e.g., required permissions, whether the workspace must be empty) and does not help differentiate from other delete tools like delete_document or delete_organization, which could lead to incorrect tool selection.

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 explains workspace_id as 'L'ID de l'espace de travail à supprimer' (the ID of the workspace to delete), which adds minimal semantic value beyond the input schema (which already defines it as a required integer). With 0% schema description coverage, more detail could have been provided, such as how to obtain the ID or any constraints (e.g., cannot delete the default workspace).

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 'Supprime un espace de travail' (Delete a workspace), which is a specific verb-resource pair. It effectively distinguishes from sibling tools like create_workspace, modify_workspace, and describe_workspace.

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 includes an explicit warning about irreversibility and deletion of all associated data, which informs when to use it (only when full deletion is intended). However, it does not provide explicit guidance on when not to use it or suggest alternative tools for related tasks like archiving or disabling a workspace.

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