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

Annotations only supply destructiveHint=true; the description adds substantive behavior beyond that: access is lost immediately, open assigned items become unassigned and are recorded, and placed items persist read-only for other members. These are exactly the consequential side effects an agent needs to warn the user about.

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?

One sentence, front-loaded with the core action and the workspace disambiguation, followed by the consequence clauses. No filler; every clause carries actionable meaning.

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?

No output schema exists, so the return-format burden is light, and the description fully covers the mutation's consequences for a destructive one-parameter tool. Combined with the 100% schema coverage, an agent has everything needed to call it correctly and explain the outcome.

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 100% and the single project_id parameter is already documented with its source (list_shared_projects). The description adds no additional parameter detail, so the baseline 3 applies.

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?

States a specific verb (leave) and resource (AccountHub shared project), and explicitly disambiguates from the Slack workspace sibling concept. An agent can distinguish this from list_shared_projects, invite_to_shared_project, or manage_slack_channel without opening any schema.

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?

Clearly signals when this applies via the explicit '(shared project) — NOT a Slack workspace' scope, which routes the agent away from workspace-leave tools. However, it does not name alternative tools or prerequisites (e.g., that membership must exist), leaving that to inference.

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