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

Adds behavioral context beyond annotations: describes permanent vs session login; explains that no-arg call returns a link. Annotations indicate idempotent and non-destructive, which description aligns with.

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?

Single paragraph, front-loaded with target audience and purpose. Efficiently covers key info, though includes some procedural detail that could be streamlined.

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?

Covers main use cases and parameter, but lacks explicit mention of error handling, token validation, or response format. For a 1-param tool with no output schema, description is adequate but incomplete.

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 coverage is 0%, but description fully compensates: explains optional token parameter, when to provide it (JWT from browser), and what happens if omitted. Adds meaning beyond schema definition.

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?

Description clearly identifies the tool as authentication for IDE agents, specifying it handles login via browser and token. It distinguishes from siblings like 'connect' by explicitly mentioning 'MCP.AI for IDE agents (Cursor, etc.)'.

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?

Provides two usage scenarios: permanent config method and session-only token method. Tells when to call without args to get a link. Could be stronger by explicitly stating when not to use, but covers main cases.

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