render_episode

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The description gives no indication of side effects, whether it is read-only, what it returns, or any operational behavior. It is missing entirely.

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 extremely short, but it is under-specified rather than concise. It lacks necessary context and does not front-load key information. It reads as a placeholder rather than a useful description.

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 low complexity (one parameter, no output schema, no annotations), the description should still provide meaningful context. It fails to explain 'pending media provider or QA gate' or what action the tool performs. An agent cannot correctly call this tool based on the given information.

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 single parameter, project_dir, has no schema description (coverage 0%) and the description does not explain its meaning or format. With zero attribution of semantics, the agent cannot know what value to provide.

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 'Report pending media provider or QA gate' is vague about the tool's action. The verb 'report' is ambiguous and does not convey what the tool does concretely (e.g., render, generate, list). It does not differentiate from siblings like qa_episode or create_episode. The purpose is unclear and the name 'render_episode' suggests rendering, but the description talks about reporting, which may be misleading.

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 guidance on when to use this tool versus alternatives. It does not mention any conditions, prerequisites, or when not to use it. The description is a single sentence with no context, so an agent cannot decide between render_episode and siblings like qa_episode or generate_assets.

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