unity_queue_info

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

The description clearly indicates this is a read-only information retrieval operation, listing the specific data points returned. However, since no annotations are provided, the description carries the full burden. It does not mention any potential side effects or prerequisites beyond the port parameter.

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 two sentences: the first clearly states the action and outputs, the second provides usage context. Every sentence is necessary and informative, with no wasted words.

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 simple input schema (one optional parameter) and no output schema, the description adequately covers the tool's purpose and return values. It could optionally mention that the queue state is for multi-agent coordination, but it already does so. The tool's simplicity means completeness is high.

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?

The input schema already provides a description for the 'port' parameter, and schema description coverage is 100%. The description adds context about the parameter's purpose (parallel-safe routing) but does not repeat schema information. This adds value without redundancy.

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 uses specific verb 'Get' and resource 'state of the multi-agent request queue', listing concrete details (total queued requests, active agents, per-agent queue depths, completed cache size). This clearly distinguishes it from sibling tools which are mostly about Unity editor operations.

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 explicitly states it is useful for monitoring when multiple agents work on the same Unity project, providing a clear context of use. However, it does not explicitly state when NOT to use it or mention alternatives.

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