Get Queue Metadata

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

Annotations already indicate readOnlyHint=true, so no contradiction. The description adds context by explaining the expand parameter's effect and giving a concrete use case, going beyond what annotations provide.

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 concise with no wasted words. It front-loads the main purpose and then provides details in a logical order. Every sentence adds value.

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 context signals (2 params, no nested objects, output schema present), the description covers the tool's purpose, return values, and expand usage. However, it could improve by explicitly stating that this is the general queue metadata tool versus more specific queue tools like queue_get_fields.

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 good parameter descriptions. The tool description adds extra meaning by explaining how to use the expand parameter for a practical purpose (resolutions for issue_close), which is not present in 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 tool returns detailed metadata about a specific queue, listing specific information like name, description, default type/priority, and optional expanded data. It distinguishes itself from sibling tools like queue_get_fields and queue_get_versions by being the general metadata endpoint.

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 a specific usage example: using expand=['issueTypesConfig'] to get available resolutions for the issue_close tool. However, it does not explicitly differentiate when to use this tool versus other queue-related siblings like queue_get_fields or queue_get_versions.

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