List sprints for a board

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

With no annotations, the description carries the full behavioral disclosure burden. It clearly conveys a read-only listing operation and discloses the state filter, but it does not mention pagination behavior via startAt/maxResults, potential errors, or what data is returned for each sprint.

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 one short, front-loaded sentence with no filler. It states the main action, the resource, and the optional filter in a compact and immediately scannable way.

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?

The tool has four parameters, no annotations, and no output schema, so the description should compensate by explaining pagination parameters and the result shape. It only covers the state filter, leaving meaningful gaps that an agent would need to guess or infer from parameter names.

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 description coverage is only 50%; boardId and state are described in the schema, but startAt and maxResults have no descriptions. The tool description repeats the state enum in prose but adds no meaning for the pagination-related parameters, so the agent must rely on parameter names and defaults to infer their purpose.

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 uses a specific verb ('List') with a clear resource ('sprints on a board') and adds an optional state filter, making the action unambiguous. It is easily distinguished from sibling tools like get_sprint or list_boards because it targets all sprints for a given board.

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 the tool: when you want the sprints belonging to a specific board, optionally narrowed by state. However, it provides no explicit comparison to alternatives such as get_sprint for a single sprint or create_sprint for new sprints, and it does not state when not to use this tool.

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