create_worksheet

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

The description adds no behavioral context beyond the action itself. The annotation destructiveHint=true signals potential destructive impact, but the description does not explain what could be destroyed, whether existing sheets are overwritten, or if the operation is reversible.

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?

At six words, the description is extremely concise and front-loaded. Every word contributes functional meaning, with no filler, repetition, or irrelevant detail.

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 that this is a simple two-parameter create operation, the description covers the core purpose and is minimally viable. However, it leaves gaps: no return value is described, no duplicate/error behavior is mentioned, and parameter details are absent. The annotation and schema provide some context but do not fully compensate.

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?

The schema has 0% description coverage for parameters, and the description does not define filepath or sheet_name. The parameter names are self-explanatory to some degree, but the description does not compensate for the missing schema details by clarifying how filepath identifies the workbook or how sheet_name is used.

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 'Create new worksheet in workbook' states a specific action and resource, clearly distinguishing it from sibling tools like create_workbook, copy_worksheet, or delete_worksheet. However, it does not explicitly contrast it with alternatives or add any scope constraints, so it falls slightly short of a top score.

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?

No explicit when-to-use or alternative guidance is provided. The intended use is implied by the verb 'Create' and the resource 'worksheet', but the description does not mention prerequisites, duplicate-handling scenarios, or when to prefer a different sibling tool.

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