jira_search_issues

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

Annotations already disclose that this is a read-only, idempotent, open-world, non-destructive operation. The description adds that results default to most recently updated, which is useful behavioral context, but it does not cover authentication needs, pagination behavior, or return characteristics.

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?

It is a single front-loaded sentence with no wasted words. The core action and default behavior are stated immediately.

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?

For a six-parameter search tool with full schema coverage and complete safety annotations, the description is largely sufficient. It could be slightly richer about result behavior, but the missing details are mostly covered by structured fields or obvious from the tool name.

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 already documents all six parameters, including JQL, site, email, fields, api_token, and max_results. The description mentions JQL and the default ordering but adds no further parameter semantics beyond the schema.

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 gives a specific verb and resource: search Jira issues, specifically via JQL. It is clearly distinct from jira_get_issue and jira_create_issue, though it does not explicitly name those siblings.

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?

It implies usage by saying the tool searches issues with JQL and defaults to recently updated results. However, it does not state when to use this instead of jira_get_issue or other Jira tools, and gives no exclusions or prerequisites.

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