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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false and openWorldHint=true, so the mutation/open-world profile is covered. The description adds one thing annotations cannot express — the required `profile:connect` scope — which is genuinely useful, but it says nothing about send limits, failure modes, or that notes are a one-shot resource (all of which only appear inside the schema).

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 short, front-loaded sentences with no filler beyond the opening line, which duplicates the title verbatim rather than stating something new. Efficient, though the wasted first line costs it a point.

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 non-idempotent, open-world write tool with no output schema, an agent gets the permission requirement but little else from the description; the surrounding mechanics (target selection, note exhaustion, refusal errors) live only in the schema. Adequate but with clear gaps.

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?

Although the reported coverage signal is 0%, the schema itself carries rich inline documentation for both `target` variants (thread/contact/profile, with errors like recipientUnavailable and profileAmbiguous) and for `note` (character limits, connectionRefused). The description adds no parameter meaning beyond the `profile:connect` scope, so the schema is doing nearly all the work.

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 a specific action and object: 'Invites a profile to connect with the account link,' which is clearer than the tautological title. It does not distinguish itself from write-side siblings like messages_send or contacts_update, but no sibling offers an invite/connect capability, so an agent can still place it.

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?

There is no when-to-use guidance, no exclusions, and no routing to alternatives. The single prerequisite callout ('Needs `profile:connect`') is a permission fact, not usage guidance for choosing this tool over the messaging or contact tools.

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