github_issues_list_milestones

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

Without annotations, the description carries the full burden. It does not disclose that the tool is read-only, returns a list, or supports pagination and filtering via parameters. The behavior is implied but not explicitly stated.

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 very concise (two words), but this underspecification reduces its helpfulness. It is not verbose, but it sacrifices clarity and completeness. Every sentence should earn its place; here, there is only a fragment.

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?

Given the absence of an output schema and the complexity of list tools (pagination, filtering), the description is insufficient. It does not mention that results are paginated, that milestones belong to a specific repository, or how output is structured. It should at least state 'List milestones for a repository'.

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 100%, so the baseline is 3. The description adds no additional meaning beyond the schema; it does not explain the purpose of parameters like 'state', 'sort', or 'direction' beyond what the schema already provides.

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 'List milestones' clearly states the action and resource. It uses a specific verb and resource, and while it doesn't explicitly mention the repository scope, the required parameters 'owner' and 'repo' in the schema imply it. It is distinguishable from sibling tools like 'get_milestone' or 'list_labels_for_milestone'.

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 on when to use this tool versus alternatives like 'github_issues_get_milestone' for a single milestone or 'github_issues_list_labels_for_milestone' for labels. The description lacks any context on prerequisites or exclusions.

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