ghl_contact_add_remove_from_business

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=true, so the safety profile is given. The description adds the useful point that a null businessId strips the association, which explains how one tool covers both add and remove, and it discloses the bulk endpoint. It does not describe failure/partial-success behavior on batch operations or what the response looks like.

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-loaded but wasteful: the title phrase appears twice in a row, one instance with a stray space before the period. The endpoint/version metadata is compact and useful. Roughly a third of the text is pure repetition.

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-body-parameter bulk mutation with a fully documented nested schema and annotations covering safety, the description is passable but thin. It never mentions the 50-contact batch ceiling, the all-or-nothing vs per-ID behavior, or that locationId scopes the operation, all of which matter for a bulk write with no output schema.

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%: ids (max 50), businessId (nullable, null removes association) and locationId are all documented in the schema. The description's null note duplicates the schema rather than adding format or constraint detail. Baseline 3 is appropriate when the schema carries the parameter burden.

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 restates the tool name twice verbatim ('Add/Remove Contacts From Business') without a fuller verb+object explanation of what 'add/remove from business' means operationally. It does reveal the key mechanic (null businessId removes the association) and names the endpoint POST /contacts/bulk/business, which signals a bulk contact-to-business assignment. No differentiation from nearby tools such as ghl_contact_update or ghl_business_get_businesses_by_location.

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?

No statement of when to use this versus ghl_contact_update (which likely also sets businessId) or any bulk alternative, and no prerequisites (location scoping, permissions). The only guidance-shaped content is the null-businessId idiom, which is a parameter behavior rather than tool selection advice.

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