Create a Google Doc

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

Beyond the annotations, the description discloses that the tool returns the document id and URL and requires the Google Drive connector. This is useful operational context. It could add more about overwrite/duplicate behavior, but creating a new doc is adequately implied.

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?

Two concise sentences: main purpose with examples, return value, and connection prerequisite. Every sentence earns its place with no redundant restatement of the title or schema.

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 create tool with fully covered parameters, the description provides everything needed: what it creates, example uses, return values, and setup requirement. Even without an output schema, the return info is explicitly stated.

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 input schema already describes both parameters (title and text) at 100% coverage, so the baseline applies. The description adds that text is optional and gives example content types, but does not meaningfully expand on parameter formatting or 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 names a specific verb ('Create'), a specific resource ('a new Google Doc in the user's Drive'), and a clear scope (title + optional body text). This clearly differentiates it from create_sheet, create_drive_folder, append_to_doc, and update_doc.

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 gives concrete example use cases (export ad copy, creative brief, report) and states the prerequisite that Google Drive must be connected. It does not explicitly mention when to prefer a sibling like append_to_doc or update_doc, but the usage context is clear.

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