linear_getProjectIssues

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

No annotations present. Description relies on 'Get' to imply read-only, but does not disclose pagination, default limit, data freshness, or any side effects. Adequate but minimal transparency.

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?

Single sentence, 17 words, front-loaded. No wasted words. Could be slightly improved with a list of filters, but very concise.

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?

No output schema and minimal description. Missing context like pagination behavior, default values (e.g., limit 25, includeCompleted true), and return format. Adequate for a simple retrieval tool but could be more informative.

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% with clear parameter descriptions. The description adds 'PM-friendly filters' but does not provide additional meaning beyond what the schema already conveys. 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?

Description clearly states it gets issues for a project and lists PM-friendly filters. Could differentiate more from sibling tools like getCycleIssues or searchIssues, but purpose is specific and not a tautology.

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?

Description implies use for project management filtering but does not provide explicit guidance on when to use this tool versus alternatives like getIssues or searchIssues. No exclusion criteria mentioned.

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