jira_sprint_list

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

No annotations provided, so the description bears full burden. It discloses output format (YAML) and optional state filtering, implying a read-only operation. It lacks details on error handling or pagination beyond the limit parameter, but for a straightforward list tool, transparency is adequate.

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 two sentences: the first states the core function and optional filter, the second adds output format and CLI mirror. No redundancy, front-loaded, every sentence adds value.

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 3 parameters with full schema descriptions and no output schema, the description covers output format and CLI mirror. Missing details like pagination behavior or error handling, but the limit parameter and state filter are adequately documented. Overall sufficient for the tool's simplicity.

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%, so baseline is 3. The description reiterates the optional state filter but does not add substantial meaning beyond the schema. It does not explain the parameters in more depth, so score remains at baseline.

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 'List sprints on an agile board' with optional filtering by state, and mentions output format (YAML) and mirrors a CLI command. This distinguishes it from sibling tools like jira_sprint_create or jira_sprint_update.

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 context for usage: optional state filter and default limit. It mentions mirroring a CLI command, which aids understanding. However, it does not explicitly state when not to use this tool or mention alternatives, but the context is clear for this simple listing tool.

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