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

Goes well beyond the destructiveHint/idempotentHint annotations by disclosing the blast radius (webhook endpoint is deleted, register tags keep their refs) and by clarifying that the connected app lifecycle is outside this tool (revoked in Partner Hub). It also names the required privilege and a confirmation protocol, all things annotations cannot express.

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 tight clauses lead with the destructive action and its blast radius, then the out-of-band consequence, then the authorization/confirmation caveat. No filler sentences and nothing redundant with the annotations.

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 single-parameter destructive tool with no output schema, the description covers action, side effects, scope limits, required role, and user-confirmation protocol. Nothing an agent needs before calling 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 orgId (public id from list_orgs, omittable for single-org keys) is already fully documented in the schema. The description adds no syntax, format, or edge-case detail about orgId, 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?

Specific verb (Remove) + resource (organization's POS connection) with the scope boundary made explicit: it also removes the webhook endpoint the connection manages, but leaves register tag refs intact. This is enough to distinguish it from sibling set_pos_connection, get_pos_connection, and delete_webhook_endpoint.

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 two concrete preconditions that gate invocation: the caller needs the admin role, and the agent must confirm with the user first. It does not name an alternative tool (e.g. set_pos_connection for reassignment) or state when not to delete, so it stops short of full when/when-not guidance.

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