list_sprints

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It reveals pagination limits, the cap at OPENPROJECT_MAX_PAGE_SIZE, and the use of next_offset. It also notes a clear error message if the Backlogs module is missing. It does not detail return format or authentication requirements, but covers the key behavioral aspects for a list operation.

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 concise, consisting of three sentences that are front-loaded with the purpose. Each sentence adds necessary information: purpose, module requirement, and pagination details. No fluff or redundant content.

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 no output schema, so the description should explain what is returned. It only says 'list Backlogs sprints' without detailing the output structure or fields. It also does not clarify what 'visible to the current token' means in terms of filtering. This leaves the agent guessing about the return shape, making it incomplete.

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 0%, so the description must add parameter meaning. It explains that limit is capped at a default of 50 and that offset should use the returned next_offset for pagination. This adds significant value beyond the schema. It does not mention that offset is 1-based or explain default values further.

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 tool lists Backlogs sprints visible to the current token. It uses the verb 'list' and specifies the resource 'Backlogs sprints'. However, it does not explicitly distinguish itself from the sibling tool 'list_project_sprints', which likely lists sprints for a specific project, so clarity is high but not perfect.

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 mentions the prerequisite of the OpenProject Backlogs module and says unavailable instances return a clear error, providing some guidance. It also explains pagination with limit and offset. However, it does not explicitly state when not to use this tool or suggest alternatives like list_project_sprints for project-specific queries.

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