notebook_add_drive

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions that this 'adds' a source, implying a write operation, but doesn't specify whether this requires specific permissions, what happens on success/failure, or if there are rate limits. The description lacks crucial behavioral context needed for safe and effective use.

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 efficiently structured with a clear purpose statement followed by a parameter list. Every sentence earns its place, though the parameter explanations could be slightly more detailed given the 0% schema coverage. The information is front-loaded and appropriately sized for the tool's complexity.

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 that there's an output schema (which handles return values), no annotations, and 0% schema description coverage, the description does an adequate job. It covers the purpose and parameter semantics reasonably well, but lacks behavioral transparency and usage guidelines. For a write operation tool with no annotation support, this leaves significant gaps in understanding how to use it safely and effectively.

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 description coverage is 0%, so the description must compensate. It provides clear semantic meaning for all four parameters: 'notebook_id' (Notebook UUID), 'document_id' (Drive document ID from URL), 'title' (Display title), and 'doc_type' (doc|slides|sheets|pdf with default 'doc'). This adds significant value beyond the bare schema, though it could benefit from more detail on format constraints.

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 the action ('Add Google Drive document as source') and identifies the resource ('Google Drive document'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'notebook_add_text' or 'notebook_add_url', which perform similar 'add source' operations but with different source types.

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 no guidance on when to use this tool versus alternatives like 'notebook_add_text' or 'notebook_add_url', nor does it mention prerequisites such as needing proper authentication or access to the Google Drive document. It simply states what the tool does without contextual usage information.

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