gitea_list_sprint_tasks

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

No annotations are provided, and the description only states the verb 'List', which implies a read operation. It lacks details on behavioral traits such as pagination, defaults, authentication requirements, or what happens when the milestone parameter is omitted.

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 sentence with no unnecessary words; it is front-loaded with the verb and resource, making it efficient and easy to parse.

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?

For a listing tool with five optional parameters and an output schema, the description is minimally adequate. However, the lack of parameter documentation and behavioral details leaves gaps that could hinder correct invocation, especially given the limited context from annotations.

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?

With 0% schema description coverage, the description should compensate but only mentions the milestone parameter. The other four parameters (limit, state, labels, dotenv_path) are left unexplained, providing minimal value beyond the schema.

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 identifies the verb 'List', the resource 'Gitea issue work items', and the scope 'for one sprint/milestone', distinguishing it from similar sibling tools like gitea_list_work_items.

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 usage for a specific sprint/milestone but provides no explicit guidance on when to use this tool versus alternatives such as gitea_list_work_items or gitea_create_work_item.

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