add_sheet

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

No annotations exist, so the description carries full burden. It does not disclose behavioral traits such as whether the tool requires authentication, if it modifies state, what happens on failure, or if it returns the new sheet ID.

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 sentence, but it sacrifices necessary detail. While concise, it omits critical information about parameters and behavior, making it under-specified for effective use.

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 has 4 parameters, no output schema, and no annotations, the description is far too minimal. It fails to explain the tool's behavior, return values, or how parameters affect the operation, leaving substantial gaps.

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?

With 0% schema description coverage, the description must add meaning. It does not mention any parameters (spreadsheet_id, title, row_count, column_count) or their defaults, leaving the agent with only the parameter names and types.

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 adds a new sheet/tab to an existing spreadsheet. The verb 'add' and resource 'sheet/tab' are specific, and it distinguishes itself from sibling tools like create_spreadsheet (creates new spreadsheet) and delete_sheet.

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 usage guidance is provided. The description does not specify when to use this tool vs alternatives (e.g., duplicate_sheet), nor does it mention prerequisites like requiring write permissions or the spreadsheet existing.

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