Create an account connection link

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

Annotations only declare the generic write/non-destructive/openWorld profile; the description adds the decisive behavior an agent could not infer: single-use link, fifteen-minute expiry, human-click-required OAuth flow, and the required post-condition check via list_accounts. That is exactly the context annotations cannot carry.

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 sentences, zero waste, and the critical constraint (this is a human OAuth flow, not an API connect) is front-loaded before the operational instructions. Every sentence earns its place.

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 annotations plus an output schema present, the description covers everything else an agent needs: who performs the authorization, link lifetime and single-use nature, and the verification step. No material gap remains for a 2-parameter, zero-required tool.

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 both parameters are already documented in the schema, including the scoping note that the network travels inside the token. The prose adds no parameter syntax, format, or constraint beyond that, so 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?

The description states a specific verb and artifact — it returns a single-use connection link — and immediately frames it as an OAuth handoff rather than an account-connection action. It also names the sibling used for verification (list_accounts), so an agent can place it precisely among the account/connection tools.

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 explicit when-to-use (hand the link to the user, ask them to open it in a browser), an explicit when-not (you cannot connect the account yourself; do not claim success until list_accounts shows it), and names the verification alternative. Nothing is left to inference.

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