get_connection_link

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

The annotations already establish that this is a safe, read-only, idempotent operation. The description adds meaningful behavioral context: the generated link must be opened by the user in a browser because OAuth cannot be completed autonomously. It does not mention link expiration or single-use behavior, but the core human-in-the-loop trait is disclosed.

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?

The description is a single, front-loaded sentence with no filler. Every clause contributes either the action, the user-browser requirement, or the reason it must be sent to a human.

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 simple read-only link generator with a fully described single parameter and no output schema, the description covers the essential context an agent needs. It could optionally mention link expiry or that the connection is only completed after the user finishes OAuth, but it is largely complete.

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 input schema fully documents the single 'provider' parameter with an enum and a clear description. The tool description does not add syntax or selection guidance beyond the schema, so the baseline of 3 is appropriate.

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 ('Generate') and resource ('a link') and explains the exact purpose: connecting a new social account. It is clearly distinct from sibling tools like list_connections because it focuses on initiating a new OAuth connection rather than listing existing ones.

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 usage context: use this when a user needs to connect a new social account and OAuth requires human browser interaction. It does not explicitly name alternatives or when not to use it, but the intended scenario is unambiguous.

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