Create Doc

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

Annotations declare readOnlyHint=false and destructiveHint=false. The description adds behavioral details beyond annotations: mentions document body starts at index 1, total length of a new empty doc is 2, and explains index structure. No contradictions.

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 well-structured: first sentence states purpose, then provides technical details and workflow. It is not overly verbose, though the technical detail about indices could be slightly compressed. Front-loads key information.

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 complex Google Docs API context, the description provides essential creation behavior and a clear workflow for building rich documents. The presence of an output schema (context signal) means return value explanation is unnecessary, so the description is sufficiently complete.

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?

Input schema covers all 3 parameters with descriptions, providing 100% coverage. The description adds minimal extra meaning beyond mentioning 'optional initial plain text content' for the content parameter, which is already clear from 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?

Clearly states 'Creates a new Google Doc and optionally inserts initial content' with a specific verb and resource. Distinguishes from sibling tools by describing subsequent steps using batch_update_doc and inspect_doc_structure, which are also in the sibling list.

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?

Provides explicit workflow guidance: after creation, use batch_update_doc with end_of_segment=true, then inspect_doc_structure. This helps the agent choose the right tool for subsequent steps. However, it does not explicitly state when not to use this tool or list alternatives for creation.

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