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

The description discloses behavioral traits beyond annotations: it distinguishes between permanent (header config) and session-only login, explains the token parameter's meaning, and notes that calling with no args returns a link. This is consistent with idempotentHint=true and readOnlyHint=false, adding useful context.

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 packed into two sentences with a clear structure (Best/Option), efficiently conveying setup and usage. It could be more organized, but it avoids unnecessary fluff.

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 an authentication tool with one optional parameter and no output schema, the description covers the main workflow, including both permanent and session configurations. It doesn't describe return values or error conditions, but the provided context is sufficient for the tool's simplicity.

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?

Although schema_description_coverage is 0%, the description thoroughly explains the single 'token' parameter: it should be a JWT pasted from the browser, and explains the no-args case. This gives meaning beyond the schema's bare 'token' string.

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 a user by logging in via browser and copying an access token, with a token parameter for session login. It distinguishes itself from sibling tools by being the dedicated authentication endpoint.

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?

It explicitly instructs when to call with no args to get the link, when to pass a token after pasting, and recommends adding the token as a header for permanent access. This gives clear usage directions and alternatives, even though it doesn't name sibling tools.

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