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

Goes well beyond the destructiveHint annotation: it explains cascade semantics (a removed direct Site may persist via a member Client; a removed Client may leave independently attached Sites/topics), idempotent behavior ('absent membership stays absent'), and that the Portfolio and underlying entities/scan history survive. It also discloses refusal conditions (wrong kinds, cross-Account IDs) and auth requirements.

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?

Front-loads verb and resource, then layers constraints and caveats in short clauses. Dense but every sentence carries distinct information; slightly packed with multiple constraints in one run-on sentence.

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?

With an output schema present, return values need no explanation, and the description fully covers cascade behavior, idempotency, non-deletion guarantees, ID constraints, prerequisite helpers, and auth. Nothing an agent needs to call this correctly is missing.

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 75%, and the description adds a combined constraint not expressible per-field in the schema: '1–100 distinct IDs total across clientIds/siteIds/topicIds'. It also ties portfolioId to the required-ID pairing, adding meaning beyond the raw 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?

Specific verb (remove) plus resource (Client/Site/topic membership) and scope (agency Account Portfolio). It is immediately distinguishable from the sibling add_members_to_portfolio, and the 'in one call' phrasing conveys the batch nature without ambiguity.

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?

Gives clear workflow guidance: resolve IDs via list_clients/list_sites_and_topics and use get_portfolio before/after changes, plus prerequisites (Account access) and the fact that no Scan is launched. It lacks an explicit 'when not to use this vs add_members_to_portfolio' exclusion, but the context is strong.

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