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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It only says 'Add rows,' offering no details about whether the operation is append-only, requires specific permissions, handles optional sheetName, or what happens on duplicate or mismatched values. The behavior is minimally clear but lacks critical context.

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 a single, front-loaded sentence with no unnecessary words. It is concise and easy to parse, though it sacrifices completeness. From a pure structure standpoint, it is efficient, but the brevity leaves out essential details.

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?

The tool has three parameters, no annotations, and no output schema, so the description needs to compensate. It fails to explain the parameters, any prerequisites, or the result of the operation. The description is too sparse to be considered complete for an AI agent to invoke 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 description coverage is 0%, and the description does not explain any parameters. It gives no hints about what fileId, values, or sheetName mean or how they should be used. The word 'rows' vaguely maps to 'values' but does not clarify the array-of-arrays structure or the role of sheetName.

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 action (Add rows) and the specific resource (Excel file in OneDrive), making the tool's purpose immediately understandable. It also distinguishes from the sibling tool append_to_sheet by specifying the file type and storage location, which is likely a different spreadsheet service (e.g., 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?

There is no guidance on when to use this tool versus alternatives like append_to_sheet or append_to_doc. The description only states what it does, leaving the agent without explicit context for selection among similar append tools.

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