Zephyr: Get priorities

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

Annotations already declare readOnlyHint/idempotentHint and destructiveHint false, so the safety profile is covered. The description repeats the schema's truncation note but then contradicts the default-pagination behavior by promising 'All priorities' for an empty parameter set.

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 organized with toolset, parameters, and examples, but the parameters section repeats the input schema nearly verbatim and the maxResults note is verbose. It is structured but not particularly concise.

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 simple read-only list operation with an output schema and optional filters, most invocation details are present: defaults, projectKey format, and paging examples. However, the incorrect 'all priorities' example leaves a gap in how to page through or truly retrieve all results, so an agent could invoke it with the wrong expectation.

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 100%, so the baseline is 3, and the description's parameter section largely duplicates the schema. The examples add combination scenarios, but the third example assigns incorrect semantics to the default maxResults value, making the guidance unreliable.

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 opens with a specific verb and resource: 'Get Zephyr Test Case priorities with optional filters' and reinforces it with a 'Toolset: Priorities' label. This is enough to distinguish it from sibling zephyr_get_projects/zephyr_get_statuses, though it doesn't explicitly contrast with them.

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?

Usage is implied through examples and optional-filter descriptions rather than stated explicitly. There is no direct statement of when to choose this over alternatives, and one example is misleading: {} is labeled 'Get all priorities' even though maxResults defaults to 10.

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