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

Annotations already declare destructiveHint=true, openWorldHint=true, and idempotentHint=false, so safety is covered structurally. The description adds genuinely new operational context beyond that: the Business subscription requirement for the owner and all members, and the availability/sign-in constraint that determines whether a queue actually rings anyone.

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?

Three short sentences with the core purpose front-loaded first, followed by the prerequisite and the availability caveat. No filler, no repetition of the title, and each sentence carries distinct information.

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?

This is a complex mutation with 7 parameters, two enums, upsert semantics, and no output schema. Rich annotations cover the safety profile, but the definition omits parameter meaning and, most importantly, how an upsert decides between creating and editing, leaving the agent under-informed for a destructive write.

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?

All 7 parameters have 0% schema description coverage, and the description explains none of them. It says nothing about how id selects edit-vs-create, what name does, how overflow or strategy enums behave, or the meaning of auto_record and max_wait_seconds. The schema is entirely undocumented and the description does not compensate.

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 pair and resource ("Creates or edits a queue"), mapping cleanly onto the tool name upsert_queue and title "Set up a queue". It is distinguishable from resource-different siblings like upsert_hours and upsert_menu, but it never explicitly contrasts itself with them, so it stops short of a 5.

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 by the prerequisites (owner and members need Business), which tells the agent when a call will succeed. However, there is no guidance on when to prefer this over alternatives, no when-not conditions, and the critical create-vs-edit trigger is left unstated, so guidance is only partial.

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