getJiraBoardIssueData

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description usefully signals that the source can be board, backlog, or both, and that results can be filtered/capped, but it says nothing about pagination behavior or how defaults are applied despite startAt/maxResults existing. Some added value over annotations, but thin.

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?

A single, front-loaded sentence with no filler or repetition. It is efficiently sized, though its brevity comes partly at the cost of detail rather than from tight editing of richer content.

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 6-parameter tool with 17% schema coverage and no output schema, the description leaves significant gaps: pagination limits (startAt/maxResults defaults), the fields projection, and the required boardId are unaddressed. The read-only annotations do lower the behavioral burden, but the parameter-level information an agent needs to call this correctly is largely missing.

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 only 17% — just the 'source' enum has a description. The description's 'count and JQL filtering' vaguely gestures at maxResults and jql, and 'board, backlog, or both' mirrors the source enum, but boardId, startAt, maxResults semantics/defaults, and the fields projection parameter remain unexplained in both places. Compensation for the coverage gap is minimal.

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 names the resource (work items/issues) and the scope (a board, its backlog, or both), which is clearer than a bare title. However, it is a noun phrase with no verb, and it does not distinguish itself from the closely related sibling searchJiraIssuesUsingJql, which it partially overlaps with by citing 'JQL filtering'. The purpose is inferable but not crisply stated.

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?

There is no explicit when-to-use guidance and no mention of alternatives. The phrase 'with optional count and JQL filtering' lists capabilities rather than telling the agent when this tool should be chosen over searchJiraIssuesUsingJql or getJiraBoardSprintData. The agent must infer the selection criteria from the name alone.

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