search_issues

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

No annotations are provided, so the description carries the full burden. It reveals only that it performs a search via JQL, without disclosing return format, pagination behavior, or whether any side effects occur. Since 'search' implies a read-only operation, this is somewhat apparent, but the description adds no further context about limits or output.

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 six-word sentence, 'Search Jira issues using JQL,' that is efficient and front-loaded. Every word contributes to conveying the core purpose without redundancy.

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?

The tool is relatively simple with two fully documented parameters and no output schema. The description explains the basic action but lacks usage guidance and behavioral details such as pagination behavior or return format. Given no annotations, a bit more context would improve completeness, but the essential operation is clear.

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%, as both parameters (jql, maxResults) have descriptions. The description's mention of 'using JQL' aligns with the jql parameter but adds no additional meaning beyond the schema. Baseline 3 is appropriate because the schema already documents parameters fully.

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 'Search Jira issues using JQL' clearly states a specific verb (search) and resource (Jira issues) with a method (JQL). It distinguishes this from siblings like get_issue (single issue) and get_sprint_issues (sprint-specific queries) by indicating a flexible JQL 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 no explicit guidance on when to use this tool versus alternatives. It does not mention exclusions, prerequisites, or cases where get_issue or get_my_issues might be more appropriate. The JQL search intent is implied but not contrasted with sibling tools.

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