remove_issues_from_sprint

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Remove issues from a sprint' implies a destructive mutation, but it fails to specify critical details: whether this requires admin permissions, if it's reversible, what happens to the issues afterward (e.g., moved to backlog or deleted), or any rate limits. This leaves significant gaps for safe and effective tool invocation.

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 zero waste—'Remove issues from a sprint' is maximally concise. Every word earns its place by directly conveying the core action and target, making it easy to parse quickly without unnecessary elaboration.

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 tool's complexity (a destructive mutation with 2 parameters), lack of annotations, 0% schema coverage, and no output schema, the description is incomplete. It omits essential context: behavioral traits (e.g., side effects, permissions), parameter details, and expected outcomes. For a mutation tool, this inadequacy increases the risk of misuse by an AI agent.

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 0% description coverage, with two required parameters ('sprintId' and 'issueIds') undocumented. The description adds no meaning beyond what the schema provides—it doesn't explain what these IDs represent, their format, or constraints (e.g., issueIds must be from the same project). With low schema coverage, the description fails to compensate, leaving parameters semantically unclear.

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 issues from a sprint' clearly states the verb ('Remove') and resource ('issues from a sprint'), making the purpose immediately understandable. It distinguishes from siblings like 'remove_project_item' by specifying the target resource as 'issues' and context as 'sprint'. However, it lacks specificity about what 'remove' entails operationally (e.g., unassigning vs. deleting).

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., issues must be in the sprint first), exclusions, or related tools like 'add_issues_to_sprint' or 'update_issue' for reassignment. Without such context, the agent must infer usage from the tool name alone.

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