Append text to a Google Doc

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the safety profile is covered. The description adds the 'Hermoso can reach' limitation and clarifies the non-destructive nature by saying 'append', but doesn't disclose error behavior or side effects. With openWorldHint=true, the description adequately supplements but doesn't go beyond what annotations expect.

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?

Single sentence that front-loads the core action and scope. The phrase 'Hermoso can reach' is slightly verbose but necessary to convey the limitation. Minimal waste; could be trimmed slightly but is efficient.

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 append tool with two parameters and no output schema, the description covers the essentials: what it does, how to get the ID, and the reachability constraint. Error cases are not described, but given the low complexity and annotations, this is adequate.

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 covers 100% of parameters, but the description adds meaning beyond schema. The schema's documentId description only mentions 'from create_doc', while the tool description extends it to include 'list_drive_files', providing a more accurate and complete source. Text description is straightforward.

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 the verb 'append' and resource 'Google Doc', and further narrows scope to docs Hermoso can reach (created or user-provided). Distinguishes from siblings like create_doc, update_doc, and read_doc by focusing on appending to the end and specifying how to obtain the documentId.

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 guidance on when to use: when appending to the end of a reachable doc, and offers two methods to source the documentId (from create_doc or list_drive_files). It does not explicitly exclude alternatives like update_doc, but the scope is clear enough for correct selection.

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