workiva_create_sheet

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

With no annotations provided, the description carries the burden of disclosing behavior. It explains parameter-specific behavior (e.g., name is optional and Workiva assigns one, index -1 appends), which adds transparency. However, it does not disclose potential side effects like sheet reordering when an index is specified, or any permissions required.

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 highly concise and well-structured: a one-sentence summary followed by a clear Args list. Every sentence adds value, with no wasted words.

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?

The description covers the necessary parameters and the core action, and an output schema exists to explain return values. It lacks guidance on error cases or prerequisites, but for a straightforward create operation, it is largely complete.

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%, yet the description fully compensates by explaining each parameter's purpose and default behavior: spreadsheet_id is the UUID, name is optional with auto-assignment, and index uses -1 to append. This adds significant meaning beyond the bare 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 the tool's action with a specific verb and resource: 'Create a new sheet in a spreadsheet.' It is distinct from sibling tools like workiva_list_sheets, workiva_get_sheet, and workiva_copy_sheet, making the purpose unmistakable.

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 when to use the tool (when you need to create a sheet in a spreadsheet) but offers no explicit guidance on alternatives, such as when to use workiva_copy_sheet instead of creating from scratch. Context is clear but exclusions are not mentioned.

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