jira_list_boards

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

No annotations provided, so the description carries full burden. It only states the tool lists boards with optional filtering, omitting behavioral traits like pagination (max_results), rate limits, permissions, or whether archived boards are included. Minimal disclosure.

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?

Single sentence, front-loaded, and concise with no extraneous information. Every word adds value.

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?

No output schema exists, but the description does not indicate what the tool returns (e.g., board IDs, names, types) or how results are structured. For a list tool, this is incomplete without additional context.

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 67% (board_type and project_key have descriptions; max_results does not). The description adds no additional meaning beyond the schema for the documented parameters and does not explain max_results behavior, default, or range.

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?

Description clearly states the tool lists Jira Agile boards with optional project filtering. The verb 'List' and resource 'Jira Agile boards' are specific, and it distinguishes from sibling tools like jira_get_board (singular) and jira_get_board_issues (issues in a board).

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 usage for listing boards but provides no explicit guidance on when to use this tool versus alternatives (e.g., jira_get_board for a single board). No exclusions or when-not-to-use are given, though the context is clear.

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