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

Goes well beyond the annotations by disclosing the consent gate: the contact is notified, decides whether to proceed, and nothing reaches the sought person until they agree, plus the request sits in a 'pending' state. That explains openWorldHint concretely. It does not reconcile destructiveHint=true — no mention that the notification can't be unsent, whether the request can be withdrawn, or whether duplicate requests are blocked.

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?

Three front-loaded sentences: purpose, then behavior, then trigger — nothing is buried. Slight redundancy between 'Ask one of the member's own contacts to introduce the member to someone' and the final trigger sentence, but it is minor.

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 7-parameter mutation with no output schema, the description covers the core mechanics (pending request, notification, recipient consent) adequately, and the schema documents every parameter. It stops short of describing what a successful call returns (a request id, a confirmation message) or how the request can be cancelled.

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%, so the baseline applies. The description reinforces the meaning of broker_contact_id ('member's own contacts') but says nothing about target_contact_id, request_note, person, project, or dry_run, so it adds only marginal semantics over the schema.

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 and resource: asking one of the member's own contacts to make an introduction by creating a pending request. The scope ('member's own contacts', 'pending') clearly separates it from discovery-style siblings such as connections_contacts_find_warm_path, though no sibling is named explicitly.

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?

The closing sentence gives an explicit trigger: 'Call this when the member asks a named contact for an introduction,' which makes the invocation context unambiguous. There is no when-not guidance, no named alternative (e.g. use find_warm_path first to pick who to ask), and no prerequisite about resolving contact ids.

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