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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so 'Read-only, no side effects' merely restates structured data and earns no credit. The description does add genuine behavioral context beyond annotations: the links land the recipient already authenticated and trigger the action immediately, which explains what consuming the output does. It stops short of describing what the call actually returns (a single link, a list keyed by action, any expiry).

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?

Two sentences, front-loaded with the core contract before the usage instruction, and the action enumeration is compressed into a single list. Slightly dense, but every clause carries information and nothing is 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?

With no output schema and only two optional, fully-documented parameters, the description does most of the remaining work: it explains what the returned URLs do and which actions they cover. The one gap is the shape of the response — whether the call returns all links at once or the agent must select one — which the agent has to infer from the action list.

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% and both parameters (person, project) are optional and fully documented in the schema, so the baseline of 3 applies. The description mentions neither parameter and adds no information about how acting-as a person or choosing a workspace affects which links come back.

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 states what the tool produces — deep-link URLs that land the member signed-in and immediately open a specific action — and enumerates the concrete actions (import Google contacts, import from a file, post a deal, browse deals, add the connector). That makes it clearly distinguishable from the action siblings like connections_import_google_contacts or connections_deal_create, which perform the actions rather than hand out links. It falls short of a 5 only because the operative verb is implied ('hand one to the member') rather than stated as 'returns deep-link URLs for X'.

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 a direct usage instruction — 'Hand one to the member in chat instead of describing the steps' — which is exactly the decision an agent needs to make. It also points to a specific alternative source, connections_pulse's next_actions, which already carry these links on the relevant action, implicitly telling the agent to check pulse first. No explicit 'do not use when' clause keeps it from a 5.

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