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

Annotations indicate readOnlyHint=false (mutation) and idempotentHint=true. The description elaborates on the mutation by describing how it can set a permanent config header or a session-only token, and that calling with no args returns a login link. It does not explicitly state side effects like modifying server configuration, but the permanent token option implies that. No contradiction 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 a single paragraph but packed with necessary details. It is front-loaded with the purpose and then branches into two usage modes. It is slightly dense and could benefit from bullet points, but every sentence earns its place and there is no fluff.

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?

Given only one optional parameter, no output schema, and rich annotations, the description covers all needed aspects: how to authenticate (browser login, token retrieval, config header), invocation modes (with/without token), and session vs permanent behavior. It is complete and actionable for an agent.

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 has 1 param (token) with 0% description coverage. The description compensates fully by explaining the token is optional, should be a JWT, and that it can be passed after the user pastes it, or omitted to receive a link. This adds crucial meaning beyond the bare 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 states the tool's purpose: authenticate for IDE agents (Cursor, etc.) via browser login. It specifies the verb 'authenticate' and the resource (access token), and distinguishes it from siblings like connect and toolkit_info by focusing on the token-based authentication flow.

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 explains when to use which option: 'Best: add it to this server's config as a header... for a permanent, non-expiring connection' vs 'Or paste it here for a session-only login: call with { token: <jwt> }... or with no args to get the link.' This gives clear context and alternatives, effectively guiding the agent on invocation choices.

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