queues_create_queue

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

With no annotations, the description must fully explain behavioral traits, but it only says 'Create a queue.' It does not disclose side effects (e.g., idempotency, whether existing queues are overwritten), required permissions, rate limits, or asynchronous behavior. This is severely lacking for a creation tool.

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?

At three words, the description is very short but omits critical context. It is not front-loaded with useful information; every sentence should earn its place, and this single phrase does not convey enough to justify its brevity.

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 that this is a creation tool with only 2 parameters and no annotations, the description should provide more context such as what the queue is, any constraints, and typical outcomes. The presence of an output schema does not compensate for the lack of behavioral and usage guidance. The description is far from complete.

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%, so both parameters are documented there. The description adds no extra meaning beyond what the schema already provides (e.g., that 'name' can have a .fifo suffix for FIFO queues, and 'region' defaults to configured region). 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?

The description 'Create a queue.' clearly indicates the verb and resource, and it distinguishes from sibling tools like queues_list_queues or queues_send_message. However, it lacks specifics such as whether the queue can be FIFO, which is hinted in the schema but not mentioned here.

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?

No guidance is provided on when to use this tool versus alternatives like queues_activate or queues_create_credentials. The description does not mention prerequisites, when not to use it, or related tools.

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