Get Board Issues

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

Annotations already indicate readOnlyHint=true, and the description confirms a read operation ('Get'). It adds behavioral context about JQL filtering and pagination parameters (start_at, limit). No contradictions.

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 structured with a clear opening sentence, followed by an Args list and Returns. It is reasonably concise, though the Args section could be trimmed if the schema already covers details.

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 presence of an output schema and detailed parameter schemas, the description adequately covers the return value ('JSON string with pagination info') and main functionality. It lacks error handling or rate limit info, but these are not critical for most use cases.

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 coverage is 100% with detailed descriptions for each parameter (e.g., JQL examples). The description's 'Args' list merely restates parameter names without adding new meaning, so it does not significantly enhance 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 clearly states the verb 'Get' and the resource 'all issues linked to a specific board filtered by JQL'. It distinguishes itself from sibling tools like jira_get_sprint_issues or jira_search by focusing on board-specific issues with JQL filtering.

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 provides context on when to use (board_id and JQL filter) but lacks explicit guidance on when not to use or alternatives. It does not differentiate from similar tools like jira_search or jira_get_sprint_issues.

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