export_weekly_csv

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

With no annotations, description discloses parallel scraping behavior, min_hours filtering, and output formats. Does not mention potential rate limits or data freshness, but adequately covers key behaviors.

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 focused sentences, each providing essential information without redundancy. Front-loaded with main purpose, then usage constraints and options.

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 date range, format, parallel scraping, and min_hours filter. Lacks details on return format structure and error handling, but sufficient for basic use.

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?

All parameters have schema descriptions (100% coverage). The description adds value by explaining the 7-day limit tied to end_date, parallel parameter speed implications, and min_hours filter purpose.

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 it retrieves time tracking data for a date range in CSV/JSON. Implicitly distinguishes from siblings like 'export_today_csv' by specifying a date range, but could explicitly differentiate.

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 says maximum 7 days per request and advises splitting longer periods. Also mentions parallel scraping for faster retrieval. Lacks explicit when-not-to-use or alternative tools.

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