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

Annotations declare readOnlyHint=false, openWorldHint=true, idempotentHint=false and destructiveHint=false, so the safety profile is covered structurally. The description adds genuine context beyond that: this only initiates a flow, the actual connection completes out-of-band when the user opens the URL, and the whatsapp onboarding omission changes behavior on the connect page.

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?

Four sentences, front-loaded with the purpose and the returned-URL action, and each platform note earns its place. Slightly dense but no 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?

For a 6-param initiation tool with no output schema and full annotation coverage, the description covers the flow's side effects, per-platform inputs, and how to consume the result. It could say a bit more about failure/expiry of the generated URL, but nothing essential is missing.

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 the per-parameter descriptions already state 'Required for telegram/bluesky' and detail the whatsapp enum, so the description largely restates the schema. It does add the omission-behavior nuance for whatsapp onboarding, but the baseline 3 applies when the schema carries the detail.

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 verb and resource ('Generate a URL to connect a new social media profile to a profile group') and immediately clarifies it initiates the OAuth/connect flow, so an agent can distinguish it from siblings like auth_status or profile_groups_list without opening the schema.

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 clear conditional guidance per platform (bluesky → identifier+app_password, telegram → bot_token, whatsapp → optional onboarding) and explains what to do with the result ('should be opened by the user to complete the connection'). It does not name an alternative tool or state exclusions, which keeps it short of a 5.

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