list_doc_tabs

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

Describes output format (flat tree with indentation for nesting), document order, and read-only nature. Specifies OAuth scope. No annotations provided, so description carries the burden adequately.

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?

Description is three paragraphs, front-loaded with key purpose. Some redundancy but overall efficient and well-structured.

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?

Covers purpose, usage, scope, and hierarchy representation adequately for a list tool. Has output schema, so return structure not required. Minor omissions like handling of empty documents, but still 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 has 2 parameters with only 50% schema description coverage. Description does not add details about 'user_google_email' or further clarify 'document_id' beyond what's in schema. Fails to compensate for low coverage.

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 'List all tabs in a Google Doc, including nested child tabs, as a flat tree.' Explains purpose for discovering IDs, titles, and hierarchy. Distinguishes from sibling tools that require a tab_id.

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?

Explicitly says 'call this first to discover IDs, titles, and the tab hierarchy.' Provides context for when to use. Lacks explicit when-not-to-use, but guidance is clear.

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