build_storyboard

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

With no annotations provided, the description carries the full burden of disclosing side effects, requirements, or limitations. It discloses none – it does not state whether it modifies state, what inputs are needed beyond the schema, or what the output is used for.

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 a single short sentence, but it is under-specified rather than concise. There is no front-loading of critical information, and the brevity comes at the cost of utility. Every sentence should earn its place, but here there is only one sentence that earns almost nothing.

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 tool sits in a complex pipeline with 11 siblings, no annotations, no output schema, and incomplete parameter documentation, the description is grossly inadequate. An agent cannot correctly select or invoke this tool with the information provided.

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?

Schema description coverage is 0%, and the description does not explain any of the three parameters (topic, duration_sec, research_pack). The agent is left to infer their meaning and formatting entirely from the schema, which is insufficient.

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 'Build a timed shot list' states a verb and resource, but it is vague and does not clarify what a 'timed shot list' is in the context of the pipeline. It also does not distinguish itself from sibling tools like write_script or render_episode, leaving the agent uncertain about its unique role.

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. No mention of prerequisites, intended place in the workflow, or conditions that would make it the right choice over any sibling tool.

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