jira_search_issues

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

No annotations are provided, so the description must fully cover behavioral traits. It does not mention that the tool is read-only, nor does it describe pagination, rate limits, or what happens with invalid JQL. The description is too minimal to inform the agent about side effects or constraints.

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 short but incomplete. The args section abruptly ends with 'max_results: ' and no further detail. While brevity is good, the missing information makes it under-specified.

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?

Although an output schema exists, the description does not mention pagination, result ordering, or limitations of JQL search. Given the tool's complexity (JQL syntax, defaults), the description lacks sufficient context for reliable agent use.

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. It adds an example for 'jql' but leaves 'max_results' with no explanation after the colon. The description adds marginal meaning beyond parameter names.

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 verb 'Search' and the resource 'Jira issues with JQL', making the tool's purpose immediately obvious. It distinguishes itself from sibling tools like jira_get_issue (single issue) or jira_list_issue_types (list types) by specifying JQL-based search.

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?

The description provides a JQL example but fails to explicitly state when to use this tool versus alternatives (e.g., when a specific issue key is known, use jira_get_issue). No guidance on use cases or exclusions is given.

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