list_sprint_active

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

There are no annotations provided, so the description carries the full burden. It does not disclose that the parameter maxResults (default 50) may limit the number of 'all' tasks returned, nor does it mention pagination, permissions, or what happens if no active sprint exists. The word 'all' is misleading given the default limit.

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 clear, front-loaded sentence with no unnecessary words or information. It efficiently states the purpose.

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 there is no output schema, the description should clarify the return value but only vaguely says 'List all tasks' without shape or content. The misleading 'all' combined with an unmentioned maxResults default leaves the tool under-specified. It does not address edge cases like no active sprint or pagination.

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 schema has one parameter (maxResults) with no description, and schema description coverage is 0%. The tool description does not mention this parameter at all, failing to compensate for the lack of schema documentation. It also uses 'all' which conflicts with the parameter's limiting behavior.

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 ('List'), the specific resource ('tasks in active sprint'), and the scope ('assigned to current user'). This differentiates it from siblings like list_my_tasks (all assigned tasks) and list_my_board_tasks (board-specific tasks).

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 clear context for when to use it: when you need tasks in the active sprint for the current user. However, it does not explicitly exclude alternatives or mention when not to use it, though the specificity makes usage implied.

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