gitee_list_releases

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It fails to mention what the tool returns (list of release objects), whether pagination is supported (though schema hints at it), ordering, or if draft releases are included. A read operation like listing should at least state it's a safe, read-only 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 extremely concise (two words), but at the cost of missing essential context. It could be improved by adding 'for a repository' and mentioning pagination while staying short. It is not front-loaded with the most useful information.

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?

No output schema exists, so the description should explain the return format (e.g., list of release objects) and behavior like pagination. It fails to do so. With 4 parameters and no return info, the description is incomplete for an AI agent to understand the tool's full behavior.

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%, with each parameter already having a clear description (e.g., owner, repo, page, per_page). The description adds no additional meaning or context beyond what the schema provides. Baseline 3 is appropriate.

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?

Description 'List releases' is clear but vague. It does not specify that it lists releases for a repository, which is necessary to distinguish from other list tools like gitee_list_issues or gitee_list_pulls. Adding 'for a repository' would improve clarity.

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?

No guidance on when to use this tool vs alternatives such as gitee_get_release, gitee_get_latest_release, or gitee_get_release_by_tag. The description should indicate that this is for paginated listing of all releases, while the others retrieve a single release.

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