export_schedule

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

Discloses key behaviors: preserves mapping metadata 'where possible' and backs up existing XLSX before writing. Without annotations, this provides useful insights into side effects, but does not cover failure scenarios or overwrite confirmation.

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?

Two concise sentences convey the primary action and two important caveats without redundancy or irrelevant details.

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?

Covers the main function and some behavioral details, but lacks information about return values, error handling, or exact file handling (e.g., overwrite behavior beyond backup). With no output schema, additional context would improve completeness.

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?

No explanation of 'filename' or 'scheduleType' is provided. The schema defines them but the description adds no meaning, leaving users to guess the role of scheduleType (group vs. private) or the expected format of filename.

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?

Clearly states the tool exports the current schedule to XLSX, distinguishing it from import, generate, or other schedule-related tools. The mention of preserving mapping metadata and backing up existing files adds specificity.

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 usage (exporting a schedule) but does not explicitly compare with alternatives like import_schedule_file or generate_weekly_schedule. No conditions or scenarios are given, though the action is evident from the name and context.

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