sprint_add_tasks

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

No annotations are provided, so the description carries full behavioral burden, yet it says nothing about idempotency, what happens to tasks already in another sprint, whether the operation is atomic across the task array, or what errors arise for invalid task ids. For a mutation tool this is a substantial gap.

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 zero waste, but its brevity reflects under-specification rather than disciplined economy—there is room to add essential context without bloat.

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?

With no annotations, no output schema, and only partial parameter documentation, the description leaves an agent without enough information to invoke a bulk mutation safely. It should at minimum explain the effect on already-attached tasks and the failure modes.

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 only 50%, and the description adds no meaning beyond the schema's own hints ('task id such as T-007', 'sprint id such as S-001'). It does not explain whether multiple tasks may span sprints, ordering effects, or limits on the array size.

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?

States a specific verb ('attach') and resource ('tasks to a sprint'), which is unambiguous and clearly distinct from the removal sibling sprint_remove_tasks. It stops short of naming alternatives, but the action itself is clear.

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 indication of when to use this versus sprint_remove_tasks or create_sprint, and no prerequisites such as whether tasks must be unassigned first or belong to a specific project. The agent must infer everything from the name.

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