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

Annotations indicate readOnlyHint: false, idempotentHint: true, and destructiveHint: false. The description adds context that config-based auth gives a permanent non-expiring connection, while pasted token is session-only, which are behavioral traits beyond annotations. No contradictions with annotations.

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 concise (3 sentences) and front-loaded with context. Each sentence adds value: why the tool exists, the best method, and the alternative method. No verbosity or 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?

The description covers the tool's purpose, both usage modes, and parameter semantics. There is no output schema, but the tool likely returns a link or status; this is not mentioned, but it's not critical for authentication flow. Given the simplicity, the description is sufficiently 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 only parameter 'token' is fully explained: it is a JWT to paste for session-only login, and omitting it returns the login link. Schema coverage is 0%, so the description carries the full burden and does so clearly, adding meaning beyond the schema.

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 explains the tool authenticates the user by logging in via browser and provides the access token. It gives a specific process and distinguishes between config-based and session-based authentication. It does not explicitly differentiate from the sibling 'connect', but the purpose is unambiguous.

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?

The description tells when to use the config header method ('Best') vs pasting a token ('session-only'), and also when to call with no args ('to get the link'). It provides clear usage context, though it does not explicitly say when not to use this tool versus alternatives like 'connect'.

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