studio_create

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

With no annotations, the description must fully disclose behavior. It reveals that this tool creates artifacts, requires user confirmation (confirm=True), and lists many configurable options and defaults. However, it does not mention side effects, rate limits, or what happens if an artifact already exists (e.g., overwrite vs. error). The output schema exists but is not described. Still, it is fairly transparent about core behavior.

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 verbose but well-organized: it starts with an overview, lists args, then type-specific and common options, and ends with examples. It is front-loaded with the purpose. While it could be trimmed slightly (e.g., the initial 'Supports' list is redundant with the args), the structure aids readability for a complex tool with many parameters.

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 22 parameters, no annotations, and presence of an output schema, the description covers all needed context: parameter descriptions, usage constraints (confirm required), type-specific options, defaults, and an example. It is complete enough for an AI agent to select and invoke the tool 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 coverage is 0%, so the description carries full weight. It provides extensive explanations for all 22 parameters, including type-specific options per artifact_type, defaults, and examples. For instance, it defines audio_format values (deep_dive|brief|critique|debate) and infographic_style options. This adds significant meaning beyond the raw schema.

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 clearly states 'Create any NotebookLM studio artifact. Unified creation tool.' It lists nine specific artifact types, making the tool's purpose explicit. The name 'studio_create' naturally distinguishes 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?

The description provides detailed usage instructions, including required parameters, type-specific options, and the confirm parameter ('Must be True after user approval'). While it doesn't explicitly mention when not to use this tool versus alternatives, the context and examples are clear. It lacks direct comparison to siblings but is otherwise well-guided.

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