add_sheet

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

No annotations provided, so description must disclose behavior. It lists parameters and mentions dry_run, but lacks details on what happens if the sheet already exists, error conditions, or side effects beyond creation. Adequate but with gaps.

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?

Description is concise: one sentence for purpose, then whitelist note, then bullet-like Args list. Every sentence adds value, with no redundancy. Front-loaded with key purpose.

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?

No output schema, so return values not needed. Covers all parameters and usage constraint. Missing error behavior and limitations (e.g., max rows/columns), but complete enough for a simple creation tool.

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 coverage is 0%, so description must add meaning. The Args list explains all 6 parameters with clear descriptions (e.g., 'spreadsheet_id_or_url: Full Sheets URL or bare spreadsheet ID'). This compensates for missing schema descriptions, though could add constraints like row/column limits.

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?

Description clearly states 'Add a new empty sheet (tab)', using verb 'add' and resource 'sheet'. This differentiates from sibling tools like delete_sheet or duplicate_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?

Includes a whitelist note explaining when the tool is allowed ('writable_sheets is "*" or the new title is explicitly listed'), providing context for usage. Does not explicitly mention when not to use or alternatives, but the constraint is clear.

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