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

readOnlyHint=true already tells the agent this is a safe read, so the bar is lower. The description does add real value by naming the returned facets (list, delivery setting, contacts synced, last error), but it omits whether disconnected/failing integrations are included and whether results are paginated or workspace-scoped.

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?

One sentence, front-loaded with the verb and the resource, with the returned fields enumerated compactly at the end. The '(Bird...)' fragment is a slightly sloppy truncation but costs little space.

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?

There is no output schema, so the description carries the return-value burden and does list the main fields an agent would consume. It is nearly complete for a zero-parameter list tool; only the inclusion rules (connected vs disconnected, pagination) remain unstated.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. No parameter discussion is needed or expected here.

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?

States a specific verb ('List') and a specific resource ('contact tools the workspace syncs identified visitors to'), with an example provider ('Bird'). The plural 'List' contrasts adequately with the singular sibling contact_integration_get, though the tie to other siblings like contact_integration_lists (a per-integration sub-resource) is not spelled out.

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?

Usage is only implied: the description tells you the tool returns the workspace's contact integrations and their sync state, so an agent can infer it is the discovery step before contact_integration_get/update/test. It never explicitly says when to pick this over contact_integration_lists or form_integrations_list, nor any preconditions.

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