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

Beyond the annotations (destructiveHint=true, idempotentHint=true), it discloses data-retention behavior ('briefs stay with the team'), an operational precondition ('Last admin must first promote someone else'), and a non-obvious billing consequence that would otherwise be a surprise. It also directs the agent to explain continued billing before confirming.

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?

Four short, front-loaded sentences with no filler; the core action leads and the caveats follow. Efficient, though the billing sentence could be tightened.

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, non-idempotent-scope mutation tool with no output schema, it covers the critical safety and billing nuances an agent needs. Remaining minor gaps concern workspace_id semantics, which the schema partly carries.

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 coverage is 50%: workspace_id is documented only by its UUID format in the schema, while confirm carries a schema description. The phrase 'Explain continued billing before confirmation' adds some intent to the confirm flag, but the description does not fully compensate for the undocumented half.

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 uses a clear verb and resource: 'Remove your team access,' which precisely conveys that this is a self-leave operation. It implicitly distinguishes from remove_workspace_member by the possessive 'your,' but does not name any sibling explicitly.

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?

It provides meaningful conditions and prerequisites: the last-admin case must promote someone first, and funding-account holders are warned billing is not cancelled. Alternatives are not named, so it falls short of full when/when-not/alternatives coverage.

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