Linear MCP Server

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

With no annotations, the description carries full burden but only states 'Handle OAuth callback' without disclosing behavioral traits. It doesn't explain what 'handle' entails (e.g., token exchange, error handling, persistence), security implications, rate limits, or side effects. This leaves critical gaps for an OAuth-related tool.

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 extremely concise with just two words, front-loaded and zero waste. It directly states the tool's role without unnecessary elaboration, making it efficient for an agent to parse.

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 complexity of OAuth callbacks (involving authentication flows, token management, and potential errors), the description is incomplete. With no annotations, no output schema, and minimal behavioral disclosure, it fails to provide enough context for safe and effective use, especially compared to more detailed sibling tools.

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 description coverage is 100%, so the schema fully documents the single parameter 'code' as an OAuth authorization code. The description doesn't add any param-specific details beyond what the schema provides, but with only one parameter, the baseline is high. No additional semantics are needed.

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 'Handle OAuth callback' states a general purpose (handling OAuth callbacks) but is vague about what specific action it performs—it doesn't specify whether it validates, exchanges, or stores tokens. It distinguishes from siblings like 'linear_auth' (likely for initiating auth) by focusing on the callback, but lacks a clear verb+resource combination.

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?

No guidance is provided on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., after 'linear_auth'), exclusions, or how it relates to other auth or data tools in the sibling list. The agent must infer usage from the name alone.

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