Linear MCP Server

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states this creates multiple issues (implying a write/mutation operation) but doesn't address authentication requirements, rate limits, whether the operation is atomic (all-or-nothing), what happens on partial failures, or what the return format looks like. For a bulk creation tool with zero annotation coverage, this is insufficient.

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 perfectly concise at just 5 words, front-loading the essential information with zero waste. Every word earns its place by clearly communicating the core functionality without unnecessary elaboration.

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 bulk creation tool with no annotations and no output schema, the description is incomplete. It doesn't address critical behavioral aspects like authentication needs, error handling, performance implications of bulk operations, or what the tool returns. Given the complexity of bulk operations and lack of structured metadata, the description should provide more context.

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 already documents the single 'issues' parameter and its nested structure comprehensively. The description adds no additional parameter semantics beyond implying bulk capability ('multiple issues at once'), which is already evident from the array type in the schema. Baseline 3 is appropriate when schema does the heavy lifting.

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 action ('create multiple issues at once') and identifies the resource ('issues'), making the purpose immediately understandable. However, it doesn't differentiate from its sibling 'linear_create_issue' which creates single issues, leaving some ambiguity about when to choose one over the other.

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?

The description provides no guidance on when to use this tool versus alternatives like 'linear_create_issue' for single issues or 'linear_create_project_with_issues' for project-based creation. There's no mention of prerequisites, performance considerations for bulk operations, or error handling for partial failures.

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