delete_workspaces__wid__profiles

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

No annotations are provided, so the description carries full burden. 'Delete' implies a destructive mutation, but the description doesn't disclose whether this is permanent, reversible, requires specific permissions, has rate limits, or what happens to associated data. For a destructive operation with zero annotation coverage, this is a significant gap.

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 a single, efficient sentence with zero waste. It's appropriately sized for a tool with two parameters and gets straight to the point without unnecessary elaboration.

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 description coverage, and no output schema, the description is inadequate. It doesn't address critical behavioral aspects (permanence, permissions, side effects) or provide sufficient parameter context. The agent would struggle to use this tool correctly without additional information.

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 mentions 'profiles' and 'workspace' which map to the two parameters (wid, profiles), but provides no additional meaning about what these parameters represent, their format, or constraints. The description doesn't explain that 'wid' is workspace ID or that 'profiles' is an array of profile identifiers.

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 'Delete multiple profiles in workspace' clearly states the action (delete), target resource (profiles), and scope (multiple, in workspace). It distinguishes from sibling 'delete_profile' which appears to delete single profiles, but doesn't explicitly differentiate from other workspace-related delete tools like 'delete_workspaces__wid__members__id_'.

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?

No guidance on when to use this tool versus alternatives. There are multiple sibling delete tools (delete_profile, delete_profile__id__web, delete_workspaces__wid__members__id_) but no indication of when this batch deletion tool is preferred over single deletion tools or other workspace operations.

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