jira_search_issues_tool

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It states that the tool builds and executes a JQL query, implying a read operation. However, it does not mention pagination behavior, rate limits, or authentication requirements. The existence of an output schema partially mitigates the need to describe return values.

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 consists of two concise sentences. The first sentence is front-loaded with the core purpose. Every sentence adds value without unnecessary words. It is optimally sized for quick understanding.

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 11 parameters, 100% schema coverage, and an existing output schema, the description adequately covers the core functionality. It could mention default ordering or the automatic JQL generation, but it is still complete enough for an agent to use 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 description coverage is 100%, so the input schema already documents each parameter well. The description adds a crucial constraint ('At least one search criterion must be provided') that is not in the schema, but does not provide additional meaning per parameter beyond what the schema already offers.

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 'Search for Jira issues using multiple criteria' and explains that it builds a JQL query. This distinguishes it from sibling tools like jira_issue_get_tool (single issue) and jira_search_jql_tool (raw JQL). The verb 'search' and resource 'issues' are specific and unambiguous.

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 explicitly requires 'At least one search criterion must be provided,' which guides usage. It does not explicitly contrast with alternative search tools, but the siblings list implies a distinction from jira_search_jql_tool. Clear context for use is provided, though exclusions are absent.

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