linear_createIssueTemplate

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

The description merely repeats the creation action already implied by the annotations (readOnlyHint=false). It adds no extra behavioral context (e.g., permissions needed, duplicate handling, side effects). With annotations carrying the burden, the description fails to contribute meaningful disclosure.

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?

Extremely concise—one sentence—but appropriately so for a simple purpose. It is front-loaded and to the point, though it could include minimal structural hints (e.g., input vs. output).

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?

Despite having 5 params, nested objects, and an output schema, the description is minimal. It does not explain what a template is or how templateData should be structured, leaving the agent with insufficient context for correct invocation.

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 coverage is 100%, so the schema already describes all parameters. The description adds no additional parameter meaning beyond what is in the schema. Baseline of 3 is appropriate.

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 a new issue template' uses a specific verb ('Create') and resource ('issue template'), clearly distinguishing this tool from sibling tools like linear_getIssueTemplates or linear_createIssueFromTemplate. It directly states the action and object.

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 on when to use this tool versus alternatives (e.g., when to create a template vs. use an existing one). The description provides no context about prerequisites or scenarios, leaving the agent without decision support.

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