Retrieve overdue milestones from GitHub projects to track delayed deadlines and manage project timelines effectively.
Get a list of overdue milestones
| Name | Required | Description | Default |
|---|---|---|---|
| limit | Yes | ||
| includeIssues | Yes |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It states it 'gets a list', implying a read-only operation, but doesn't cover permissions, rate limits, pagination, or response format. For a tool with two required parameters and no output schema, this leaves critical behavioral traits undocumented.
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, efficient sentence with zero waste—it directly states the purpose without fluff. It's appropriately sized for a simple tool, though this conciseness comes at the cost of detail in other dimensions.
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 tool's complexity (2 required parameters, no annotations, no output schema), the description is incomplete. It lacks parameter explanations, behavioral context, and output details, making it inadequate for reliable agent use without additional inference or trial-and-error.
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 0%, so the description must compensate for undocumented parameters. It mentions no parameters at all, failing to explain 'limit' (e.g., max results) or 'includeIssues' (e.g., whether to fetch related issues). This leaves the agent guessing about input semantics beyond basic types.
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 'Get a list of overdue milestones' clearly states the verb ('Get') and resource ('overdue milestones'), but it's vague about scope and doesn't distinguish from siblings like 'list_milestones' or 'get_upcoming_milestones'. It specifies the 'overdue' filter but doesn't clarify what constitutes 'overdue' or how results are determined.
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 'list_milestones' or 'get_upcoming_milestones'. The description implies it's for retrieving overdue items, but it doesn't specify prerequisites, context, or exclusions, leaving the agent to guess based on tool names alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.