delete_workspaces__wid_

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

No annotations are provided, so the description carries the full burden. 'Delete workspace' implies a destructive, irreversible mutation, but it lacks critical behavioral details: whether deletion is permanent, requires specific permissions, affects associated resources (e.g., profiles, members), or has confirmation steps. This is inadequate for a high-stakes 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 extremely concise at two words, with zero wasted language. It's front-loaded with the core action and resource, though this brevity comes at the cost of completeness for a destructive tool.

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, 0% schema coverage, and no output schema, the description is severely incomplete. It doesn't address behavioral risks, parameter details, or expected outcomes, leaving the agent with insufficient context to use it safely or effectively.

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 schema only indicates a required 'wid' parameter of type string. The description adds no meaning beyond 'workspace'—it doesn't explain what 'wid' represents (e.g., workspace ID, name), its format, or where to find it. This fails to compensate for the schema's lack of documentation.

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 verb ('Delete') and resource ('workspace'), making the purpose unambiguous. However, it doesn't differentiate from sibling tools like 'delete_workspaces__wid__members__id_' or 'delete_workspaces__wid__profiles', which also delete workspace-related entities but target different resources.

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 no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., workspace must be empty), consequences, or when to choose other deletion tools like 'delete_workspaces__wid__members__id_' for removing members instead of the entire workspace.

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