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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=false. The description adds genuine context beyond them: 'Calls ring only members who are signed in and available' and the Business-plan eligibility gate. It does not explain partial-update behavior (the role of id when editing), what happens to existing members, or any return/result semantics, so it remains partial.

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, front-loaded with the core action, then the behavioral fact, then the plan constraint. No filler. The terse 'Business plan.' fragment is abrupt but does earn its place as a gating condition.

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 mutation tool with 7 undocumented parameters, no output schema, and only partial annotation coverage, the description is too thin. It omits how edits behave, what the strategy/overflow options mean, and any result or side-effect detail an agent would need to invoke it correctly.

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 0% across 7 parameters, so the description carries the full burden and largely fails it. 'Queue of people' loosely hints at member_ids and 'edits' hints at id, but name, overflow, strategy, auto_record, and max_wait_seconds are left entirely undocumented, including the semantics of the two enums.

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?

States a specific verb and resource: 'Creates or edits a queue of people on this account.' The upsert semantics are clear and consistent with the name. It does not differentiate itself from the other upsert_* siblings (upsert_hours, upsert_menu, upsert_receptionist), but the resource itself is unambiguous.

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 explicit when-to-use vs alternatives guidance; it doesn't tell the agent how to choose between this and upsert_receptionist/upsert_menu. The 'Business plan' note is an eligibility prerequisite rather than usage routing, which is useful but not what this dimension asks for.

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