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

The description goes beyond annotations by explaining the token expiration behavior: config-based header is permanent and non-expiring, while passing the token is session-only. This adds useful context not present in annotations (idempotentHint: true, destructiveHint: false). However, it does not disclose what happens after authentication (e.g., side effects like storing the token internally) or if there are any side effects on subsequent requests. The annotations already indicate idempotency and non-destructiveness, so the description adds moderate value beyond that.

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, uses clear formatting with colons and a best-practice tip. It is front-loaded with the target audience (IDE agents) and then quickly covers the two usage modes. Every sentence adds value, covering purpose, usage, and parameter semantics without unnecessary fluff. The structure flows logically from explaining the intended use to providing detailed instructions.

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 the tool's simplicity (one optional parameter, no output schema) and the presence of annotations, the description is fairly complete. It explains the authentication flow, the two usage modes, and the parameter semantics. However, it could be more complete by mentioning what the expected response looks like (e.g., success message) or any error scenarios, but given the simplicity, this is not a major gap.

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 schema has one optional parameter 'token' with no description and 0% schema coverage. The description compensates by explaining that 'token' is a JWT passed after the user pastes it, and that calling without arguments returns the login link. This is crucial semantic information that the schema lacks. The description fully explains the parameter's meaning and usage, effectively compensating for the schema's lack of detail.

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: authenticating the user by providing a login link or accepting a token. It explicitly mentions 'log in in the browser, copy the access token' and explains two modes: permanent config-based auth and session-only token paste. While it doesn't explicitly compare to sibling tools like 'connect', the purpose is specific and actionable, distinguishing it from other tools by its focus on authentication.

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 clear usage guidelines: when to use the browser flow (with no args to get the link), and when to paste the token (with { token: '<jwt>' }). It also mentions an alternative of adding to config for permanent connection, which serves as guidance on when not to use session-only login. However, it does not explicitly mention when to use 'connect' as an alternative, leaving some ambiguity with sibling tools.

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