get_render_queue_status

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

With no annotations provided, the description carries full responsibility for disclosing behavior. It does this by revealing the key limitation: it 'currently returns guidance for Adobe Media Encoder rather than live queue telemetry.' This is honest and useful, though the exact nature of the 'guidance' output remains unspecified.

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 short sentences with no filler. The primary purpose is front-loaded, and the clarifying caveat about Adobe Media Encoder earns its place by preventing a false expectation of live telemetry.

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 zero-parameter status check with no output schema, the description covers the essential context: what the tool reports and what it actually returns today. It does not describe the exact structure of the returned guidance, but this is a minor omission for such a simple tool.

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 tool has zero parameters and the schema has 100% coverage of its empty properties. Per the baseline for zero-parameter tools, the description does not need to add parameter semantics, and it correctly does not attempt to invent any.

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 states a specific verb and resource: 'Reports whether render queue monitoring is available.' It further clarifies the tool's actual behavior by noting it returns guidance for Adobe Media Encoder rather than live queue telemetry, making its purpose unambiguous and distinguishing it from any telemetry-related siblings.

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 implies that the tool should be used to check monitoring availability, and the caveat warns users not to expect live telemetry. However, it does not explicitly state when to use this tool versus alternatives, nor does it name any sibling tool that provides live queue data.

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