github_list_releases

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

Since there are no annotations, the description must disclose all behavioral traits. It only mentions it lists releases, but does not describe details like pagination, sorting, or how session_name affects behavior. The default for max_results is mentioned, but the broader behavior remains opaque.

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 focused sentence followed by a compact parameter list. Every line adds value with no redundancy or filler.

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 is simple and has an output schema, so return value details aren't needed. However, without annotations, the description lacks context about pagination, rate limits, or when to choose this over related release tools, making it only minimally complete.

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 compensates by providing brief meanings for each parameter (e.g., 'Repository owner', 'Maximum releases to return') and includes the default for max_results. However, session_name is only vaguely described as 'GitHub session to use', leaving room for ambiguity.

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 all releases for a repository' with a specific verb and resource. It distinguishes itself from sibling release tools like github_get_release and github_get_latest_release by indicating it lists all releases rather than a single one.

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 is provided about when to use this tool versus alternatives such as get_release or get_latest_release. The description simply states what it does without contextual exclusions or recommendations.

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