op3_downloads_timeseries

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions that records are verbose and the tool is a low-level feed, implying a read-only, data-intensive operation. However, it does not explicitly state whether the tool is read-only or detail authentication requirements, leaving some gaps.

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 exceptionally concise, with only four sentences that each serve a distinct purpose: stating the tool's function, describing output, placing it among siblings, and providing usage guidance. There is no redundant information.

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?

Given the absence of an output schema, the description does a good job of conveying the return structure (time, country, app, device) and the need to limit results. However, it does not fully describe the output format or pagination behavior, which would be helpful for complete understanding.

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 are described in the schema (100% coverage), but the description adds value by explaining the output structure and verbosity, and by providing context for the limit parameter. This goes beyond the schema's descriptions to help the agent understand parameter impact.

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 clearly states that the tool fetches raw download records for a show over a date range, returning individual events (time, country, app, device). It explicitly distinguishes itself as the low-level feed behind other tools, differentiating from sibling tools like op3_show_downloads and op3_top_countries.

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 provides explicit guidance on when to use this tool ('when you need to filter by episode or a specific date window') and when to prefer alternatives ('For totals or geography summaries, prefer op3_show_downloads / op3_top_countries'). It also advises to keep the limit low due to verbosity.

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