sigma_add_workbook_schedule

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

Annotations already indicate readOnly=false and destructive=false, so the write/non-destructive nature is known. The description adds context about 'scheduled export' and points to docs for the body schema, but does not disclose side effects, permissions, or response behavior. No contradiction with annotations.

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 concise and front-loaded with the primary action, and the second clause points to documentation. It has no wasted words, though the external doc reference is a slight evasion of inline explanation.

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 tool has a free-form nested body, open-world hint, and no parameter documentation in the schema. The description defers all body schema details to external docs, making it incomplete for an agent to invoke correctly without additional lookup.

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%, and the description does not explain workbook_id or the body structure beyond saying 'See Sigma docs for schedule body schema.' Given the body has additionalProperties=true, the agent gets no meaningful parameter semantics from the description.

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 uses a specific verb ('Create') and resource ('scheduled export for a workbook'), clearly distinguishing it from sibling tools that list, delete, or create report schedules.

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?

It clearly implies use for creating a workbook schedule, but it does not explicitly state when to use this over alternatives like list_workbook_schedules or create_report_schedule, nor does it mention any exclusions or prerequisites.

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