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

The description adds meaningful context beyond the annotations: it explains the token acquisition flow, the permanent vs session distinction, and the config header option. It aligns with the idempotent hint and non-destructive annotation, with no contradictions.

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?

Two sentences cover the primary login flow, permanent config option, session token option, and no-args fallback. The first sentence is somewhat long but remains readable and every clause contributes to the usage.

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 simple tool with one optional parameter and no output schema, the description covers all usage modes and the config interaction. It could mention response/return behavior, but that is not critical given the tool's simplicity.

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?

With 0% schema description coverage, the description fully compensates by explaining the 'token' parameter as a JWT from the browser, showing example usage with `{ token: '<jwt>' }` and the no-args alternative. This gives the parameter complete semantic meaning.

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 authenticates the server via browser login and token exchange, specifying two modes (config header vs session token) and the no-args link retrieval. It does not explicitly distinguish from sibling tools like 'connect', so it falls short of a 5.

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?

Provides actionable instructions for both permanent and session-based authentication, including the no-args call to get a login link. However, it lacks explicit guidance on when not to use this tool or how it relates to the 'connect' sibling, so it earns a 4.

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