jira_search_issues

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It correctly states the tool is read-only, which is a key safety characteristic. However, it does not describe return format, pagination behavior, or potential errors, so transparency is limited.

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 two sentences with no filler: the core purpose is stated first, and the read-only note adds a valuable safety trait. It is concise, front-loaded, and every word earns its place.

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 has no output schema, no annotations, and sparse parameter documentation. The description only states the search capability, failing to explain what the result looks like, how limit and startAt control pagination, or any other behavioral context needed for correct invocation.

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?

The schema covers 0% of parameter descriptions, and the tool description does not explain any parameters. The phrase 'using JQL' hints at the jql parameter, but limit and startAt are completely undocumented, leaving the agent without necessary invocation details.

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 resource 'Jira issues' with the method 'JQL', distinguishing it from sibling tools like jira_get_issue and jira_get_my_issues. The explicit 'read-only' note further clarifies the tool's intent and scope.

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 implies the tool should be used when a JQL query is needed and asserts it is read-only, but it does not explicitly compare to alternatives such as jira_get_my_issues or jira_get_issue. There are no clear 'when not to use' instructions or alternative tool suggestions.

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