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

The description does not disclose behavioral details such as side effects, whether it opens a browser, or what happens after successful authentication. The annotations indicate it is not read-only and is idempotent, but the description adds little beyond the login instruction.

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 verbose and poorly structured, mixing instructions and explanations. It contains unnecessary phrases like 'MCP.AI for IDE agents (Cursor, etc.)' and the flow is not clearly organized. A more concise and structured description would be beneficial.

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 does not explain the full authentication flow, including what happens when a token is provided (e.g., validation, success/failure responses). It only mentions that without a token it returns a link, but the outcome of providing a token is unclear. The absence of an output schema further limits completeness.

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 parameter 'token' is described: 'call with { token: "<jwt>" } after the user pastes, or with no args to get the link.' This explains how to use the token and the behavior when omitted. However, the token format is not fully specified.

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 indicates the tool is for authentication by logging in and obtaining a token, but it is not stated explicitly and is mixed with instructions. It mentions 'log in in the browser' and 'copy the access token', which suggests the purpose, but the phrasing is convoluted.

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 provides some usage guidance by differentiating between permanent configuration and session-only login via this tool. It says 'Best: add it to this server's config as a header... Or paste it here for a session-only login.' However, it does not clearly state when to use this tool versus alternatives.

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