linear_removeIssueFromRelease

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

Annotations indicate idempotentHint: true and destructiveHint: false, but the description does not expand on behavioral aspects such as what happens to the issue after removal (e.g., it remains in the backlog) or required permissions. It adds no context beyond the 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 that is front-loaded and contains no unnecessary words. It is concise but could include a bit more context without being verbose.

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 simplicity of the tool (2 parameters, removal operation) and the presence of an output schema and clear annotations, the description is minimally adequate. However, it lacks details about the effect on the issue or any preconditions, which would help an agent invoke it correctly.

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% with clear parameter descriptions ('The ID or identifier of the issue to remove' and 'The ID of the release to remove the issue from'). The tool description does not add further meaning, but the schema already provides sufficient information, so 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 'Remove an issue from a release' clearly states the action (Remove) and the resource (issue from a release). The tool name also reflects this, and among siblings there are similar tools for adding issues to releases and removing issues from projects, which are distinct.

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 provided on when to use this tool versus alternatives like 'linear_addIssueToRelease' or when it is appropriate. There is no mention of prerequisites (e.g., the issue must be in the release) or conditions.

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