List GitHub Milestones

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is fully covered and the bar is lower. The description adds useful payload context (completion percentages, due dates), but says nothing about pagination via limit, default state filtering, or what happens when repo/owner are omitted (auto-detect).

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?

A single front-loaded sentence with zero filler. It is efficient, though the terseness leaves the remaining dimensions thin rather than adding structure.

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 read-only list tool with rich annotations, an output schema that defines return shape, and 80% schema coverage, the description supplies the one thing structured fields do not: the salient content of each milestone (completion percentage, due date). Nothing critical to correct invocation is missing.

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 80%, so the schema already documents repo, owner, limit, and state — including the 'LEAVE EMPTY to auto-detect from git' hint. The description adds no parameter-level detail beyond implying a repository scope; only use_test_db is undocumented anywhere, which is minor. Baseline 3 applies.

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?

States a specific verb (List) and resource (GitHub milestones) scoped to a repository, plus the notable payload fields (completion percentages, due dates). It does not explicitly distinguish itself from the sibling get_github_milestone (singular) or create/update/delete_github_milestone, though the plural 'List' implies the distinction.

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 versus get_github_milestone for a single milestone, or versus get_github_issues/get_github_prs in the same GitHub family. The only contextual hint is 'for the repository', which does not route the agent between alternatives.

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