linear_createIssueFromTemplate

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

The annotations already signal that this is a mutating, non-idempotent operation, and the description adds the key behavioral fact that the issue is created by applying a template. However, it does not disclose side effects such as whether template defaults are copied, whether overrides replace them, or any result details, so it only partially exceeds what annotations already convey.

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?

A single, front-loaded sentence with no filler. It states the operation and the template source immediately and spends no words on anything an agent can read from the schema or annotations.

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 8-parameter tool with a fully described schema and an output schema, the brief description plus structured fields is nearly complete for invocation. The main missing contextual element is guidance on when this should be used instead of the plain createIssue tool, but that gap is already captured in usage guidelines.

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 baseline applies. The description itself names no parameters, but the schema already documents all eight fields clearly, including which overrides are optional, so the description does not need to add parameter-level meaning.

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 uses a specific verb and resource ('Create a new issue') and the qualifier 'from a template' clearly separates it from the sibling linear_createIssue, which creates an issue from scratch. It tells an agent exactly what resource and operation this tool performs.

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 given about when to choose this tool over linear_createIssue or other sibling tools. The description does not state conditions, exclusions, or alternatives, leaving the agent to infer usage from the name and schema alone.

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