ask_cluster_notebooklm

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the tool is a deprecated alias, without describing any behaviors (e.g., read-only, side effects, or response format). The agent must infer behavior from the parent tool's description, which is not referenced.

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 extremely concise, consisting of a single sentence. While it lacks depth, it is appropriately sized for a deprecated alias and contains no wasted words.

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 complexity (4 params, no annotations, output schema exists), the description is too minimal. It does not explain return values, parameter details, or usage context. The output schema may provide some structure, but the description adds no value beyond deprecation notice.

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?

The schema has 4 parameters with 0% description coverage, and the tool description does not explain any parameter meanings. For a tool with no parameter descriptions, the description must compensate, but it offers no information about cluster, question, headless, or timeout_sec.

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 it is a deprecated alias for ask_cluster(source='notebooklm'), which implies the purpose is to ask a question to a NotebookLM cluster. However, it does not explicitly explain what the tool does, relying on the user to know ask_cluster's behavior. It distinguishes from siblings by noting it is an alias, but lacks a specific verb and resource.

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 explicitly marks the tool as 'Deprecated alias', indicating it should not be used directly and that ask_cluster with source='notebooklm' should be used instead. This provides clear guidance on when not to use this tool, though it could be stronger by explicitly naming the alternative.

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