download_artifact

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

With no annotations, the description carries the full behavioral disclosure burden. It states the core action and a key constraint (artifact must be completed) and the side effect (writing to a local file), but it does not mention possible failures, overwrite behavior, or whether the output path can be a directory. This is adequate but not richly transparent.

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?

A single, front-loaded sentence with no filler. Every word contributes: 'Download', 'completed', 'NotebookLM artifact', and 'local file' are all needed and meaningful.

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?

For a simple four-parameter operation with full schema coverage and an output schema, the description is mostly sufficient. However, it does not connect to the broader artifact workflow (e.g., how to obtain artifact_id via list_artifacts or wait for completion via check_artifact_status), so an agent may still need extra inference to invoke it 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 100%, so the schema already documents all four parameters. The description repeats 'artifact' and 'local file' concepts already present in the schema without adding new semantics like file extensions, type constraints, or how artifact_id defaults to the latest artifact.

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 states a specific verb ('Download') and resource ('completed NotebookLM artifact') with a clear destination ('to a local file'). This uniquely distinguishes it from siblings like generate_artifact, list_artifacts, and check_artifact_status, which cover creation, listing, and status checking rather than retrieval to disk.

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 word 'completed' implies the tool should be used after an artifact has finished generating and likely after checking status with check_artifact_status, but this is only implied, not explicit. There is no when-not-to-use guidance or naming of alternatives, so the agent must infer the workflow from sibling names.

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