member-delete

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

Despite being a destructive operation, the description lacks disclosure of side effects, permission requirements, reversibility, or impact on workspace. No annotations compensate for this 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?

Single sentence plus tags is concise but underspecified. No front-loading of critical details; could be expanded with minimal added verbosity.

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 delete tool with two required params and no output schema, the description lacks return value info, error conditions, and post-conditions. Incomplete given no annotations.

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%, and the description does not explain the parameters (workspacePublicId, memberPublicId). The names are self-explanatory, but the tool definition adds no meaning beyond the schema.

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 action ('Deletes a member from a workspace'), with a specific verb and resource. It distinguishes itself from sibling member tools (e.g., invite, updateRole) by explicitly mentioning deletion.

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 vs alternatives. Missing prerequisites, when-not-to-use, or context about member deletion in relation to other workspace operations.

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