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

With no annotations provided, the description carries the full burden and does disclose key behaviors: it appends after the last data row, interprets values as typed (numbers/dates parse, '=' becomes a live formula), and notes the lack of a raw-text option. However, it omits details like permissions, error behavior, or return value, which are relevant 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?

Two sentences with zero filler. The primary purpose is front-loaded, followed by essential behavioral notes. Every clause adds value; no redundancy.

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?

While the description covers the core behavior and type parsing, it lacks an output schema and does not mention what the tool returns (e.g., success confirmation, row count, or error conditions). It also does not address prerequisites like existing workbook/sheet or permission needs. For a 4-required-param mutation tool without annotations, this is a notable gap.

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 description coverage is 50%, and the description adds substantial meaning to the 'values' parameter (parsing behavior, formula interpretation) beyond the schema's generic 'Rows of cell values'. It does not explain 'sheet' or 'workbookId', but those are fairly self-explanatory, and the description compensates for the most complex parameter.

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 (Add/append) and resource (rows to an Excel worksheet) with a precise placement rule (after the last row holding data). Clearly distinguishes from sibling tools like update_excel_range (modifies existing cells) and append_google_sheet_rows (Google Sheets) via the explicit Excel context and the contrast with Google Sheets.

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 clear context that this is the standard way to add new records to a tracker, implying it is for appending rather than updating. The contrast with Google Sheets ('no option to store text exactly as given') offers a usage hint for when to prefer the alternative, but it does not explicitly name sibling tools or state when not to use this tool.

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