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

Annotations already declare this as a safe read-only, idempotent, closed-world list. The description adds meaningful non-schema context: empty list semantics ('empty list = none'), the bring-your-own-key prerequisite, and the operational caveat about not concluding AI clips are unavailable. It does not describe return shape, but with readOnly annotations covering safety, this adds substantial behavioral value.

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?

Front-loaded with the core definition, but the remainder is a dense run-on covering two paths, conditional asking logic, a negative instruction, and reel integration. Every sentence carries information, but the packing hurts scannability and could be split for clarity.

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 no-param, no-output-schema list tool, the description supplies everything needed to call it and interpret results: what is listed, empty-list meaning, the alternative path, the decision rule, and how it integrates with reels. Nothing required for correct invocation is missing.

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?

Zero parameters, so baseline is 4. The schema is fully covered (100%) and there is nothing to document; the description correctly adds no parameter noise.

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 ('providers that are wired AND have a key configured by this organization'), and clearly distinguishes this key-based path from the Ignix Creator path and from reel creation via get_reel_playbook. An agent can tell exactly what this returns and how it differs from siblings like get_creator_setup or get_reel_playbook.

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?

Explicitly lays out the two ways to make an AI clip, when to ask the user which one, and what to do when only one is available ('no key → Creator; no terminal → the key'). Names alternatives (get_creator_setup, get_reel_playbook) with the conditions that select them, and includes an exclusion ('never say an AI clip cannot be done just because this list is empty').

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