Create Sheet

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

Annotations already indicate readOnlyHint=false and destructiveHint=false, so the description adds limited behavioral context. It states the tool creates or duplicates, which is consistent with annotations, but lacks details on side effects (e.g., whether duplicate overwrites, naming conflicts, or index behavior). The openWorldHint=true is not explained.

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 one sentence with a parameter list, which is concise and front-loads the action. However, it uses Python-like type hints that may not be optimal for MCP descriptions. It is relatively short with no extraneous information.

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 complexity (5 parameters, duplication logic, optional index) and lack of parameter descriptions, the description is incomplete. It does not mention return values (though an output schema exists), error cases, or uniqueness constraints on sheet names. More detail is needed for an agent to invoke it 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 must compensate. It lists parameter names and types but provides no explanation of their roles (e.g., source_sheet_name is for duplication, insert_sheet_index controls position, sheet_name is for new sheet). The parameter list is insufficient for an agent to use the tool correctly.

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 creates a new sheet or duplicates an existing one, using a specific verb and resource. It distinguishes from sibling tools like create_spreadsheet (creates a new spreadsheet) or create_doc, as it operates on a sheet within an existing spreadsheet.

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 implies that a spreadsheet_id is required, suggesting it adds sheets to an existing spreadsheet, but it does not explicitly state when to use this tool versus alternatives like create_spreadsheet or how to choose between creating new or duplicating. No prerequisites or exclusions are mentioned.

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