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

Annotations already convey that this is a write operation (readOnlyHint=false) and non-destructive (destructiveHint=false). The description adds the behavioral constraint that it only operates on sheets Hermoso can reach, which is useful scoping. However, it does not disclose side effects, error conditions, or reversibility beyond what annotations imply. Given the annotations, the description adds moderate value but not rich behavioral detail.

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 two sentences, front-loaded with the purpose, then provides sourcing guidance. It is concise, with no wasted words, and each sentence earns its place. It could arguably be a single sentence, but the structure is clear and 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 no output schema, the description covers how to get the ID and the row format. It does not mention the optional range parameter, but that is documented in the schema. It also doesn't specify return behavior (e.g., success/failure indicators), but given the operation's simplicity, this is a minor gap. Overall, the description is adequate but could mention error scenarios or result expectations.

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%, with all parameters described (rows, range, spreadsheetId). The description reiterates the rows format ('array of row arrays') and adds context on how to source spreadsheetId (from create_sheet or list_drive_files), which is beyond the schema's plain description. This adds marginal but non-critical value, so it sits at the baseline for high-coverage schemas.

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 the tool appends rows to a Google Sheet, specifying the verb (append), resource (rows to a Google Sheet), and the scope (sheets Hermoso can reach). It distinguishes from siblings like update_sheet by implying it adds new rows rather than modifying existing cells. Also, it explains how to identify the target sheet (via create_sheet or list_drive_files), making the purpose unambiguous.

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 gives clear context on when to use this tool: when appending rows. It explains how to obtain the spreadsheetId, either from create_sheet or list_drive_files, which guides the agent on prerequisite steps. However, it does not explicitly mention alternatives like update_sheet for modifying existing cells, nor list any exclusions. The context is sufficient for an agent to decide when this tool is appropriate, though explicit comparisons are missing.

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