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

Discloses persistence behavior (permanent vs session-only), the mechanism of obtaining a token via browser, and the impact on connection lifetime. This goes beyond the idempotent and destructive hints, adding valuable context about side effects.

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 compact yet comprehensive, packing multiple usage scenarios into two sentences without redundancy. All information is necessary for correct 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?

The description provides complete operational context: how to authenticate, when to use each method, and what the tool does (returns a link or accepts a token). No output schema exists, but the return behavior is implied sufficiently.

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 only parameter 'token' is explained as the JWT to paste for session login, and the optional nature is clarified by saying 'with no args to get the link'. This fully covers parameter meaning and optionality.

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: authentication for MCP.AI in IDE agents. It explains the two methods (browser login with token paste, or no args to get link) and distinguishes it from sibling tools like connect and marketplace.

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 each mode: add token to config for permanent connection, or pass token for session-only login, and calling with no args to get the login link. This provides clear guidance on invocation.

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