completeAuthLink

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

With no annotations, the description bears full burden. It discloses persistent side effects (writing to ~/.extentos/auth.json), error conditions (unknown_device_code, auth_timeout), and the polling mechanism. Minor gap: doesn't detail behavior if called multiple times with same deviceCode after success.

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?

Description is a single, well-structured paragraph. It front-loads the primary action, uses bold for important notes, and every sentence adds value. No redundancy.

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 tool with no output schema, the description adequately explains the flow, expected outcomes (token persisted), and error handling. It references the relevant sibling tool createSimulatorSession, providing complete operational context.

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 covers 100% of parameters with descriptions. Description adds context on the source of deviceCode and default/clamping behaviors for maxWaitSeconds and pollIntervalSeconds, but largely reiterates schema info. Baseline 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 clearly states the tool's purpose: polling the backend to complete user signup and persist a bearer token. It distinguishes itself from the sibling tool createSimulatorSession, which handles auth inline, by specifying when this tool is needed.

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?

Explicitly states when to use: after createSimulatorSession returns 'auth_required' with autoLink:false or after a timeout. Also warns against preemptive use and highlights that autoLink handles it by default in bundle 10+.

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