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

The description discloses behavioral traits beyond the annotations: it explains the two authentication modes (permanent via config header, session via token), that calling with no args returns a login link, and that the config approach yields a non-expiring connection. The annotations include idempotentHint: true, and the description does not contradict this.

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 somewhat verbose and starts with an audience note ('MCP.AI for IDE agents (Cursor, etc.)') before getting to the core instructions. It front-loads the purpose but could be tightened; the config sentence is a bit run-on and mixes advice with functionality.

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 usage modes well but does not explain what the tool returns upon success or failure, nor does it mention error handling (e.g., invalid token). Since there is no output schema, some indication of the expected response or side effects would make it more 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 input schema has one parameter 'token' with no description (0% coverage), but the description fully explains its meaning: a JWT to paste for session-only login, and that omitting it triggers the link-only flow. This compensates for the schema gap.

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 with specific verbs and resources: it allows logging in and obtaining an access token, with explicit instructions for both permanent and session-only authentication. It distinguishes itself from sibling tools by being the authentication utility.

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 gives explicit usage scenarios: 'Best: add it to this server's config as a header... for a permanent connection' and 'Or paste it here for a session-only login: call with { token: ... } after the user pastes, or with no args to get the link.' It clearly explains when to pass the token vs no argument, but does not explicitly mention when not to use the tool or compare to alternatives.

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