a2atlassian

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

No annotations are provided, yet the description discloses minimal behavioral information. It does not explain the pagination behavior (limit/offset defaults), the mysterious 'format' default value ('toon'), rate limits, or authentication requirements implied by the login/logout siblings.

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?

Extremely concise at two sentences with no filler. However, given the complexity (5 undocumented parameters) and lack of annotations, this brevity results in under-specification rather than efficient communication.

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?

Inadequate for a tool with 5 parameters and zero schema documentation. While an output schema exists (reducing the need to describe return values), the description provides insufficient context for the input parameters, pagination behavior, or JQL syntax requirements.

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?

With 0% schema description coverage, the description fails to compensate adequately. While 'using JQL' implies the syntax for the 'jql' parameter, it leaves four other parameters unexplained: 'project' (key vs name?), 'limit'/'offset' (pagination behavior), and 'format' (allowed values?).

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 identifies the action (search), resource (Jira issues), and method (JQL). However, it does not explicitly distinguish this from sibling 'jira_get_issue', which also retrieves issues but by specific identifier rather than query.

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?

No guidance provided on when to use JQL search versus retrieving a specific issue directly via jira_get_issue. No mention of prerequisites, required permissions, or when to prefer this over other discovery methods.

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