Get Service Desk Queues

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

Annotations include readOnlyHint: true, which matches the read-only nature. Description adds that it raises NotImplementedError on Cloud, which is important behavioral context beyond annotations. Also describes return format as JSON string with queue list and pagination metadata.

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?

Description is concise with a clear structure: one-line purpose, platform restriction, args list, returns, raises. Front-loaded with purpose, no wasted words.

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 (context indicates true) and annotations, the description is sufficiently complete. It covers the error case and return format. Could add more usage context, but current level is adequate for a read-only list tool.

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?

Input schema has 100% coverage with descriptions. Description reiterates parameters with slight additions (e.g., 'Service desk ID (e.g., '4')'), adding minimal value beyond schema. Baseline 3 is appropriate.

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 'Get queues for a Jira Service Desk' with a specific verb and resource. It distinguishes from siblings by specifying Server/Data Center only and using Jira Service Desk context, which is unique among the sibling tools.

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?

Explicitly states 'Server/Data Center only. Not available on Jira Cloud,' providing clear context on when to use. Does not compare directly to sibling tool like jira_get_queue_issues, but the restriction is a strong guideline.

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