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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is covered; the closing 'Read-only, no side effects' largely restates them. The genuine added value is behavioral: links land the member already signed-in and immediately trigger the action, which an agent could not infer from annotations.

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 tight sentences, front-loaded with the core definition and enumeration before the usage instruction. The trailing 'Read-only, no side effects' is redundant given the annotations, a small waste in an otherwise efficient description.

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 zero-parameter, no-output-schema tool, the description covers what is returned (signed-in deep links per action) and how to use them. It stops short of describing the shape of the returned collection (e.g., keyed by action versus a list), which is the one gap an agent might care about in the absence of an 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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; per the rubric this is the baseline 4. No parameter names or formats are needed.

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 concretely defines the resource: deep-link URLs that land a member signed-in and open a specific action, enumerating those actions (import contacts, import file, post deal, browse deals, add connector). It also names connections_pulse as the carrier of these links, which separates it from sibling action tools like connections_deal_create. The verb is implicit ('the contract: URLs that...') rather than an explicit 'returns the deep-link URLs', which keeps it just 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 explicit routing guidance: 'Hand one to the member in chat instead of describing the steps,' which states both the use case and the alternative it replaces. It further tells the agent where these links already surface (connections_pulse's next_actions on the relevant action), so the agent can decide whether to call this at all.

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