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

With no annotations, the description carries the full burden, and it does disclose real behavior: the job is a "sealed drop" into the supervisor's PO Box, an X-Queue-Key header is required, and there is a paid production endpoint distinct from the sandboxed MCP runtime. It omits key effects such as whether the job leaves the worker's queue, what state the item transitions to, and failure/idempotency behavior.

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 purpose is front-loaded in the first clause, but the text mixes operational detail (header, endpoint, price) with promotional noise such as "By OMENZ" and parenthetical runtime branding. Some sentences earn their place; others dilute the actionable content.

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 state-mutating queue operation with no annotations, no output schema, and five parameters of which four are undocumented. An agent cannot tell from the definition which parameters are required, what the secrecy guarantee implies for follow-up reads, or what the call returns.

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 only 20% and four parameters (reason, item_id, queue_id, worker_id) are untyped and undescribed in both schema and description. The description only clarifies that x_queue_key is transmitted as an HTTP header, leaving the meaning of the remaining fields — including which identifier is required to address a job — unexplained.

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?

"Hand a job up to the supervisor" gives a specific verb (escalate) and target (supervisor), which distinguishes it from sibling queue operations like queue_fail or queue_resolve. It does not explicitly contrast with those siblings, but the escalation semantics are clear enough to select the tool.

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?

There is no statement of when to escalate versus fail, resolve, or complete a job, and no prerequisites or constraints. The agent must infer the trigger condition from the word "escalate" alone across a dense family of queue_* tools.

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