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

Adds substantial context beyond the annotations: single-use codes, a ten-minute expiry, token lifetime until the user disconnects, and the fact that the user must accept in the browser before a token appears. The non-readonly, non-idempotent annotations are consistent with a session-establishing tool, so no contradiction. It stops short of saying what happens if a code is reused or expires mid-flow.

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?

Front-loaded with the outcome and the two numbered branches, and the expiry/token-lifetime note is placed last where it belongs. It is slightly dense with nested parentheticals ('(the Connect MCP button)', '(they have to accept it in their browser first)') that could be flattened, but no sentence is wasted.

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?

No output schema exists, and the description compensates fully by describing both possible return values (a link on the first call, a token after acceptance). It also tells the agent how to sequence calls and what to send the user, which is everything needed to invoke it correctly.

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 coverage is 100%, so the baseline is 3, but the description adds useful operational semantics: the code is 8 characters, can come from the user's screen or from the returned link, and omitting it produces a link. That connects the parameter to the two-step flow in a way the schema alone does not.

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 action and target: 'Pairs you with the user's Frapea browser tab', and names the concrete outcome ('a session token to pass on every later call'). This is clearly distinct from other connect-prefixed siblings like connect_media_folder, which deal with media rather than a browser session.

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?

Gives an explicit two-branch decision procedure: use case (1) when Frapea is already open, case (2) when it is not or 'you are not sure'. Names the alternative path, tells the agent to poll every few seconds, and states the exit condition (a token is returned).

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