linear_createRelease

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

Annotations indicate a non-readOnly, non-destructive write operation. The description confirms a creation action but adds no further behavioral context (e.g., side effects, required permissions, or constraints). No contradictions with annotations.

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 sentence of 9 words, front-loaded with the core action. Every word is necessary, and there is no redundant or irrelevant content.

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 11 parameters and an output schema, the description is minimal but sufficient. It does not discuss optional behaviors (e.g., backfilling timestamps) but the schema and output schema compensate.

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 input schema has 100% description coverage across all 11 parameters. The description adds no parameter-specific information, but baseline is 3 given high schema coverage.

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'), resource ('a new release'), and context ('in a release pipeline'). It distinguishes this tool from siblings like linear_getReleases, linear_searchReleases, etc.

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 implies when to use (creating a release), but lacks explicit guidance on when not to use or comparison with alternatives like linear_completeRelease or linear_updateRelease. No exclusions or context cues are provided.

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