jira_search_issues

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

No annotations are provided, so the description bears full responsibility for disclosing behavioral traits. It describes the JQL requirement and pagination behavior but does not mention potential errors (e.g., invalid JQL), required permissions, or response format.

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 concise with only two sentences and an example list. It is front-loaded with the core purpose, then provides usage examples and pagination hint. No redundant or filler content.

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 complexity and lack of output schema, the description covers the essential aspects: JQL requirement, examples, pagination. It could be more complete by indicating the typical return structure (e.g., list of issues with key fields), but it is sufficient for an experienced agent.

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 description's main value is adding context. It provides example JQL strings and clarifies that the jql parameter must have a filter condition. This adds meaning beyond the schema's basic text.

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 the action ('Search Jira issues'), the resource (issues), and the method (using JQL). Examples distinguish it from sibling tools like jira_get_issue or jira_get_board_issues.

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 specifies that JQL must include at least one filter condition, which is a key usage guideline. It also mentions pagination via nextPageToken. However, it does not explicitly state when not to use this tool or provide alternatives, though no direct sibling exists for issue search.

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