list_jira_issues

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

No annotations are provided, so the description must carry the burden. It discloses default returned fields, pagination via next_page_token, and ability to add extra fields. However, it does not mention rate limits, error handling for invalid JQL, or that this is a read-only operation (though implied by 'List').

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 relatively concise with a clear structure: first sentence states purpose, followed by a note on default fields, then an Args section documenting each parameter. It could be slightly more compact, but it's well-organized.

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 the tool's complexity (4 parameters, output schema exists), the description covers key aspects: default fields, pagination, and additional field selection. It lacks information on error handling or constraints, but the presence of an output schema partially compensates.

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 0%, but the description adds meaning for all four parameters: jql is a JQL query, next_page_token for pagination, max_results limits results, and additional_fields lists extra fields with an example array. This goes beyond the schema's titles and defaults.

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 tool name 'list_jira_issues' clearly indicates listing Jira issues, and the description states 'Lists Jira issues using JQL.' This distinguishes it from sibling tools like 'read_jira_issue' which fetches a single issue, and 'jira_search_users' which searches users.

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 does not provide guidance on when to use this tool versus alternatives (e.g., read_jira_issue for single issue, or Confluence search). It does not mention prerequisites or when-not-to-use scenarios.

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