List Jira Agile boards

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered without description help. The description adds one real behavioral fact — the Jira Software installation dependency — but says nothing about visibility rules, pagination, or how results are ordered.

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?

Two short sentences, front-loaded with the operation and followed by the hard prerequisite. There is no redundant or filler text; the sparseness is a completeness problem, not a conciseness one.

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 list endpoint with four entirely undocumented parameters, no output schema, and no pagination guidance, the description is too thin. An agent can see the tool lists boards but cannot tell how to filter, page, or interpret visibility scoping from the definition alone.

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%, so the description carries the full burden of explaining the four parameters, and it explains none of them. It never mentions that the call can be filtered by 'name' or 'projectKeyOrId' or that 'startAt'/'maxResults' control pagination, so an agent must infer everything from bare property names.

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?

States a specific verb and resource ('List ... Jira Software boards') with a scope qualifier ('visible'), so the agent knows exactly what resource is returned. It does not distinguish itself from the related jira_list_sprints or explain what a board contains, but the core purpose is unambiguous.

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 gives a prerequisite ('Jira Software must be installed'), which is genuinely useful context, but offers no when-to-use guidance, no exclusions, and no pointer to related siblings like jira_list_sprints. Usage is only implied by the verb 'List'.

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