get_render_queue_status

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

With no annotations provided, the description carries the full burden. It discloses a key behavioral nuance: the tool currently returns guidance for Adobe Media Encoder rather than live queue telemetry. This goes beyond a simple status check and prevents false expectations. Minor ambiguity remains about the exact return shape (boolean vs. string), but the main caveat is well communicated.

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 concise sentences. The first sentence states the primary purpose, and the second provides a critical caveat without any fluff or redundancy.

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 tool with no output schema, the description adequately covers the essential context: what it reports and its current limitation. An example return value or more explicit type information would improve it, but it is still sufficient for an agent to decide whether to invoke it.

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 (empty object), so no parameter documentation is needed. The baseline for zero-parameter tools is 4, and the description adds no unnecessary parameter details.

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 'Reports whether render queue monitoring is available,' providing a specific verb and resource. It also distinguishes itself by explicitly noting it returns Adobe Media Encoder guidance rather than live queue telemetry, which separates it from sibling tools like add_to_render_queue or start_batch_encode.

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 clearly implies when to use this tool: to check render queue monitoring availability. It also warns that it does not provide live queue telemetry, setting expectations and preventing misuse, though it does not explicitly name an alternative tool for live telemetry.

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