Search Jira Issues

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

With no output schema, the description discloses the exact return envelope {total, issues:[{key, summary, status, assignee, updated, updatedJql}]}. It goes further by explaining updatedJql's minute-flooring in the user's timezone and warning that polling is at-least-once so callers must dedupe — behavioral context the readOnly/idempotent annotations cannot convey.

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?

Three tight sentences, all load-bearing: purpose first, then return shape, then the polling semantics. No filler, and the most decision-relevant facts (return shape, dedupe) are front-loaded.

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?

Compensates for the missing output schema by fully specifying the return structure, and covers the subtle polling-increment semantics unique to this tool. Combined with 100% schema coverage of maxResults/jql, an agent has everything needed to call and consume it correctly.

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%, so `jql` and `maxResults` are already documented in the schema. The description reinforces JQL usage and shows a query template (key/updated), which adds modest value but no parameter-level detail beyond the structured data. 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 and resource: 'Search Jira issues using JQL'. The verb 'search' plus the JQL mechanism distinguishes it implicitly from jcm_getIssue (single fetch) and jcm_searchArticles (different resource), but it never names a sibling or scoping rule explicitly.

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?

Provides a concrete usage pattern for polling with `key = X AND updated > "<updatedJql>"` and warns about at-least-once semantics requiring dedupe. It does not say when to prefer this over jcm_getIssue for a single known key, so usage is implied rather than fully guided.

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