docs_add_tab

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

No annotations provided, so the description carries full burden. It explains the write operation, required access, and that it returns tab_id and a link. It does not disclose potential failure modes or idempotency, but the block format details are extensive. Overall, it provides good transparency for a mutation tool.

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 lengthy but well-structured: a clear opening sentence, a prerequisite line, then parameter explanations with blocks detailed in a bullet-like list. It is front-loaded with the main action. While comprehensive, some redundancy in the blocks examples could be trimmed without loss.

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 (string parameter for JSON blocks) and no output schema needed (tool returns tab_id and link), the description covers all necessary aspects: purpose, parameters, required access, and block format. It is complete for an agent to invoke 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 coverage is 0%, so the description must explain all three parameters. It does so thoroughly: doc_id with URL pattern, tab_title with float, and blocks with a complete specification of the JSON array format, including all supported types, flags, and examples. This adds significant value beyond the 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?

The description clearly states 'Adds a new named tab to an existing Google Doc and writes formatted content.' It specifies the action (add), resource (existing Google Doc), and output (tab and formatted content). This distinguishes it from the sibling 'docs_create_doc' which creates a new document.

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 includes a prerequisite: 'The service account must have Editor access to the target document.' It implicitly differentiates from 'docs_create_doc' by focusing on an existing doc. However, it does not explicitly state when not to use this tool or provide alternatives beyond the sibling context.

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