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

Reveals persistence behavior: permanent/non-expiring via config header vs session-only via pasted token. Also discloses that calling with no args gives a link. This goes beyond annotations which already note idempotent/non-destructive.

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?

Two sentences, somewhat dense but each clause serves a function. Could be slightly more concise but not padded.

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?

For a tool with one optional parameter and no output schema, the description covers the entire flow: login, token handling, permanent vs session, and the no-arg behavior. It does not discuss error handling but is adequate for an auth tool.

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, and the no-args case is described to get a link. Since schema coverage is 0%, the description is essential and covers both cases.

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 authentication flow: 'log in in the browser, copy the access token' and explains the two invocation modes (with token or no args). This distinguishes it from sibling tools like connect or marketplace by focusing solely on credential setup.

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 guidance on two usage options: 'Best: add it to this server's config as a header...' vs 'Or paste it here for a session-only login'. It does not explicitly compare to sibling tools but gives clear context on when to use each mode.

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