jira_search_jql_tool

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

No annotations are provided, so the description must convey behavioral traits. It states it executes a query, which is read-only, but does not explicitly confirm no side effects, permissions needed, or rate limits. The mention of supporting ORDER BY adds some behavioral detail, but more transparency about the operation's nature would be beneficial.

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 two sentences. The first states the core purpose, and the second provides usage guidance. No unnecessary words.

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?

With an output schema present, the description does not need to detail return values. It covers the tool's purpose, when to use, and basic behavior. For a tool of this complexity (JQL query execution), the description is complete enough, though it could mention pagination behavior (though schema covers parameters).

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 schema itself documents all three parameters clearly with descriptions and defaults. The description adds that the tool supports ORDER BY clauses (already part of JQL) and implies full JQL capability, but does not provide additional semantic context beyond what the schema offers. Baseline 3 is appropriate.

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 tool executes a JQL query directly, with a specific verb ('Execute') and resource ('JQL query'). It also distinguishes from the sibling tool 'jira_search_issues_tool' by noting it's for complex queries not expressible through search_issues criteria.

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?

Explicitly tells when to use this tool: 'for complex queries that can't be expressed through search_issues criteria.' This provides clear guidance on selecting between this and the sibling tool, and mentions support for all JQL operators and ORDER BY clauses.

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