linear_get_project_milestone

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

With no annotations, the description carries the burden of disclosing behavior, but it merely restates the function's name ('Get information about a specific project milestone'). It does not mention read-only nature, potential errors, authentication, or return format, providing no additional behavioral context beyond the name.

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, to-the-point sentence with no wasted words. It is concise and front-loaded, though it provides minimal additional information beyond the tool name.

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 simple get-by-ID tool with full schema coverage, the description is minimally adequate. However, without an output schema or annotations, it does not explain what is returned or clarify differences from sibling tools, leaving some gaps in context.

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% for the single 'id' parameter, which is already described in the schema. The description adds no further meaning or context about the parameter, so the baseline of 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?

The description clearly states the action (get) and resource (project milestone), and the word 'specific' implies retrieving a single item by ID, which distinguishes it from list/search siblings. However, it does not explicitly differentiate from 'get_project_milestones' or name alternatives.

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 given on when to use this tool versus sibling tools like linear_search_project_milestones or linear_get_project_milestones. There is no mention of prerequesites or contexts that would help select this tool.

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