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

With only destructiveHint=false in annotations, the description carries most of the behavioral load and does so well: it discloses the mandatory login, the read-before-write requirement, that update is a full replacement where null clears a field, the merge-vs-ignore distinction for imports, and the real-world effect on the public profile and matching. Return values and error modes are not described, and the wholesale-replacement semantics sit in mild tension with destructiveHint=false, which keeps it from a 5.

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?

The text is dense and front-loaded: ops and their semantics come first, followed by the preview/confirm protocol, then the side effects. Every clause carries information and nothing is padded. The semicolon-chained telegraphic phrasing is efficient but slightly harder to parse than plain sentences.

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 five-parameter write tool with 0% schema description coverage and no output schema, the definition covers the essentials: op semantics, the preview-confirm dance, side effects, and the destructive null-clearing caveat. It stops short of describing what get returns in detail or how the business payload fields behave, which would have closed the remaining gap.

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 0%, so the description must compensate, and it does for most parameters: it explains what each op value does, that preview defaults to on, that consent must be true, and that previewHash must accompany a confirmed write. It does not spell out the business payload's fields (clients, services, education, etc.) or the limits the schema encodes, so the anyOf/null-clearing payload remains partly opaque.

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 attaches a distinct verb to each op: get reads business details plus pending roster items, update wholesale-replaces, accept_import merges, dismiss_import ignores. That is a specific verb+resource mapping an agent can act on. It never differentiates 'my business' from near-duplicate siblings such as update_my_company or update_my_profile, so it falls short of a 5.

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?

It gives per-op usage context and a concrete write workflow: writes default to preview, and confirmation requires the same params plus previewHash, consent=true, and preview=false. It also warns that saving affects the public homepage and matching and is not auto-adopted. What it lacks is any explicit exclusion or pointer to an alternative tool when a sibling (e.g. update_my_profile, update_my_company) would be the better choice.

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