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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered. The description adds genuinely new context beyond that: removal is scoped to the saved catalog (not the community itself) and a user confirmation is required. It does not state reversibility or whether the community can be re-added.

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?

Three sentences, each carrying distinct information: what is removed and from where, the parameter preference, and the safety gate. The scope is front-loaded and there is no filler.

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?

Output schema exists, so return values need not be described. For a destructive mutation, the description covers scope, parameter selection, and the confirmation precondition, and annotations cover idempotency and destructiveness. Nothing essential to correct invocation 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 description coverage is 100%, so baseline would be 3, but the description adds real semantic value by specifying a preference ordering between communityName and communityId that the schema descriptions do not express. accountId's source (list_accounts) is already in 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?

Names a specific verb (Remove) and a specific resource (a Community) with scope narrowed to one connected X account's saved catalog. This clearly distinguishes it from the sibling add_x_community, and an agent can tell what it does without opening the 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?

Explicitly states which parameter to prefer (communityName) and the narrow condition for the fallback (communityId only on name collisions), plus a confirmation gate before calling. It does not name sibling alternatives such as add_x_community, but the operational guidance is concrete rather than implied.

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