excel_create_sheet

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

Without annotations, the description carries full behavioral burden. It discloses that the tool appends a sheet (not inserts), requires existing .xlsx, validates name characters, returns the sheet index, and raises specific errors. This is comprehensive, though it omits whether the file is modified in place or saved.

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 very concise with clearly labeled sections (Args, Returns, Raises). Each sentence serves a purpose and no unnecessary words are used. The structure aids readability.

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?

Given the tool's moderate complexity, the description covers purpose, all parameters with constraints, return value structure, and error conditions. It is self-contained and sufficient for an 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%, so the description fully compensates. For 'path', it clarifies it must be an existing .xlsx. For 'name', it specifies non-empty and forbidden characters. For 'folder', it explains optional base for relative paths. This adds significant meaning beyond the schema.

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 'Append a new sheet to the workbook.' This is a specific verb (append) and resource (new sheet), distinguishing it from sibling tools like delete, rename, or list 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?

The description does not provide guidance on when to use this tool vs. alternatives, such as creating a workbook first or when to use other sheet operations. No when-not-to-use or contextual advice is given.

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