Create media bin

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

Beyond annotations (readOnlyHint=false, destructiveHint=false), the description discloses key behaviors: folder is read inside TD (not server), empty folder yields empty pointable bin instead of error, crossfade ramps Switch's fractional index. No contradictions with annotations.

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?

Description is dense but front-loaded with the core action. It efficiently conveys the network construction, controls, and edge-case behavior. Could be slightly more structured, but every sentence adds value.

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 complexity (7 params, no output schema), the description fully covers the tool's behavior: what it builds (bin COMP with controls), how it handles empty folders, and the crossfade mechanism. No gaps in understanding.

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 coverage is 100% with descriptions for all 7 parameters. The description adds minimal additional meaning beyond the schema, e.g., explaining max_clips caps files and crossfade ramps Switch index. Baseline 3 is appropriate as the schema already provides sufficient semantic detail.

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?

Description clearly states the tool's purpose: 'Point at a folder... and build a clip BIN inside a new bin COMP'. It details the process (scan folder, create Movie File In TOPs, Switch TOP, Null TOP) and controls (Index, Next/Prev, Crossfade). Differentiates from sibling create_video_player by contrasting use cases.

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 states when to use this tool vs. alternative: 'Use create_video_player for a hand-listed playlist; use create_media_bin to ingest a whole folder for clip-based VJing.' Provides clear context for selection.

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