Read a Google Doc

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

Annotations already cover readOnly/idempotent/non-destructive, but the description adds meaningful context: the drive.file scope's reach limits, the not-found failure mode and correct recovery, and exactly what the read yields (every tab, chip text as Docs renders it, dropdowns[] feeding update_doc). This is rich disclosure beyond the annotation set.

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?

Dense and somewhat long, but front-loaded with the core action and its scope, and every clause carries a distinct operational fact (id sources, scope limits, failure handling, return shape). Minor trimming around the chip/dropdown explanation would help but nothing is filler.

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?

With no output schema, the description carries the return-value burden and does so precisely (plain text of every tab, tab headings, chip rendering, dropdowns[]). Combined with scope and error guidance, an agent has everything needed to call and interpret this tool 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 100%, so the baseline is 3, but the description adds provenance and alternation semantics the schema cannot express: documentId comes from create_doc, and the two params are an OR ('Pass documentId OR paste a Google Docs URL as docUrl').

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?

States a specific verb and resource ('Read the text of a Google Doc') and immediately bounds it: only docs Hermoso created or the user picked via the Google file picker. Names sibling tools (create_doc, list_drive_files) for the id path, so an agent can distinguish it from list_drive_files or read_sheet without opening the schema.

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?

Gives explicit when-to-use (doc created by Hermoso or handed over via the file picker), how to obtain the id (list_drive_files), and the two acceptable input routes (documentId from create_doc or a pasted docUrl). It also states the failure branch: if Google reports file-not-found, the user hasn't picked it, so ask rather than retry — that is actionable when-not guidance.

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