studio_create

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

With no annotations, the description carries the full burden. It discloses that confirm must be True after user approval, that source_ids defaults to all sources, and that language falls back to NOTEBOOKLM_HL env var or 'en'. It also notes constraints like visual_style not allowed for cinematic/short. It does not mention async behavior or how to monitor progress, but for a creation tool it provides meaningful behavioral context.

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 long but justifiably so for a 22-parameter polymorphic tool. It is front-loaded with the main purpose, then uses headings, bullet lists, and examples to organize information efficiently. No unneeded sentences – every section 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?

All 22 schema parameters are accounted for in the description, and it adds enums, constraints, and defaults. The presence of an output schema means return-value documentation can be external. The description also includes practical examples, making it complete for an agent to invoke correctly.

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%, so the description is the sole source of parameter meaning. It explains every parameter, including artifact_type with nine enumerated values and type-specific sub-options (audio_format, video_format, orientation, etc.), which goes far beyond the schema's raw defaults and anyOf types.

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 opens with 'Create any NotebookLM studio artifact' – a clear verb and resource. It then lists all supported artifact types (audio, video, infographic, etc.), making its scope explicit and distinguishing it from siblings like studio_delete and studio_revise.

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?

It is described as a 'Unified creation tool', which clearly signals when to use it for artifact creation. The examples demonstrate valid calls. However, it does not explicitly mention alternatives for revision (e.g., studio_revise) or when not to use this tool, leaving a slight gap in exclusion guidance.

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