linear_create_issues

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

There are no annotations to provide safety hints, so the description carries the full burden of behavioral disclosure. It only states that the tool creates issues, but does not mention whether the operation is atomic, how partial failures are handled, permission requirements, rate limits, or what is returned. This is a significant gap for a mutation 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 a single, front-loaded sentence with no wasted words. It is efficient, though arguably too terse to provide context beyond the core action. It earns a high score for conciseness but loses a point for being slightly under-informative.

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 simple tool complexity and complete schema, the description is minimally viable. It does not explain return values or error/partial-failure behavior, which is a gap since there is no output schema. However, for a straightforward bulk-create operation, this is an acceptable baseline.

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 schema provides 100% coverage of the 'issues' parameter and its nested properties, each with clear descriptions. The tool description adds no additional parameter information, so the baseline of 3 is appropriate; the 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 'Create multiple issues at once' clearly states the verb (create), resource (issues), and specifies the batch functionality ('multiple'), effectively distinguishing it from the sibling tool linear_create_issue. This is a specific and unambiguous purpose statement.

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 phrase 'multiple issues at once' conveys that this tool is for bulk creation, implying a contrast with single-issue creation. However, it does not explicitly name the alternative or provide exclusion criteria, though the sibling tool name makes the distinction evident.

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