create_connected_account_magic_link

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

Beyond the annotations (which only flag non-readOnly/non-idempotent/non-destructive), it adds an auth requirement ('Requires the caller OAuth token') and return semantics ('Each call returns a new link and an expiry'), reinforcing the non-idempotent behavior. It stops short of describing scopes or failure modes, so not a full 5.

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 short, front-loaded sentences; the primary action leads, followed by routing guidance and behavioral constraints. 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?

With no output schema, the description compensates by stating what a call yields (a new link plus an expiry) and the auth prerequisite. For a 3-param creation tool, nothing needed to call it correctly 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%, so the schema already documents connector, identifier, and environmentId. The description's examples ('such as Notion or Gmail') merely echo the schema, adding no meaning beyond it — the baseline 3 applies.

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 (Create) and resource (a link that connects an OAuth connector account) with concrete examples (Notion, Gmail). It also scopes the action to 'one environment' and explicitly distinguishes itself from catalog-search siblings.

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?

Names both alternatives and the condition that selects each: 'Use list_connected_accounts to see accounts that are already connected' and 'This tool does not search the catalog. Use search_connectors for that.' The agent is routed unambiguously.

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