export_times_and_leaves

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

Annotations only declare readOnlyHint and openWorldHint; the description adds the decisive behavioral fact that the endpoint requires an upstream browser session and currently fails with an explanation (not a file) under API-key auth. That auth-failure mode is exactly the kind of context annotations cannot express.

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?

Three sentences, front-loaded with what the tool produces, followed by the alternative-routing caveat and a one-word safety note. No filler; every sentence carries information the agent needs before invoking.

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-value explanation is unnecessary; the description still covers the failure mode the output schema cannot. For a 4-param, zero-required export tool, nothing an agent needs to decide or call is missing.

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 100%, so from/to/format/save_to are already documented in the schema. The description restates the date range, format choices and save path without adding syntax, defaults beyond 'csv', or path-format detail, so baseline 3 applies.

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?

States a specific verb (Download/export) and resource (declared time and leave periods) with scope (date range), output forms (CSV/XLSX), and an optional server-side save path. It is clearly distinguishable from export_projects and from list_time_entries/timesheet.

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?

Explicitly names the preferred alternatives ('Prefer list_time_entries or timesheet for reading time') and gives the condition under which this tool is the wrong choice (API-key auth fails against the upstream browser session). This is a rare, fully actionable routing instruction.

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