Workbooks Create Report Schedule

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

Annotations already disclose that this is a non-read-only, non-destructive, open-world mutation, so safety basics are covered. The description adds nothing beyond that: it doesn't say what happens on duplicate schedules, whether creation is idempotent, what permissions are needed, or what the schedule body must contain.

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?

It is a single front-loaded sentence with no padding, which is structurally clean. But at this length it is under-specification rather than true conciseness, since essential calling information is simply absent.

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?

An output schema exists, so return values need not be described. Still, for a mutation tool whose only payload is an opaque nested object, the description leaves the agent without the body contract or any behavioral context needed to call 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% and the description offers no parameter detail at all. The 'body' parameter is an untyped free-form object with additionalProperties true, so the agent has no idea what fields (cadence, recipients, format) it must supply — the description fails to compensate for a total schema gap.

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 states a specific verb and resource ('Create a scheduled export for a report'), which is clear enough for an agent to know what it does. However, it does not distinguish this tool from its close sibling workbooks_add_workbook_schedule (or workbooks_list_report_schedules), so the report-vs-workbook boundary is left to inference.

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?

There is no when-to-use guidance, no mention of prerequisites (e.g., the report must exist, required scopes), and no pointer to the alternative schedule tools. The agent gets no help deciding between this and workbooks_add_workbook_schedule.

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