tautulli_plays_by_date

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

No annotations are provided, so the description carries the full burden. It correctly describes a read operation ('Get daily play counts') but does not mention any side effects, permissions, or data limits beyond what the schema shows. The description is straightforward and accurate, but minimal.

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 a single sentence of 15 words, front-loaded with the core action ('Get daily play counts') and essential details ('broken down by stream type'). No extraneous 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?

With one parameter and an output schema present, the description provides sufficient context for a simple daily-play-count tool. It lacks mention of date formatting or handling of missing days, but the output schema likely covers return format. Adequate for its complexity.

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?

The single parameter 'days' is fully described in the input schema ('Number of days to show (default 14, max 90)'). The tool description adds no additional meaning beyond the schema, so baseline score of 3 applies due to high schema coverage.

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 'Get daily play counts over time, broken down by stream type', using a specific verb ('Get') and resource ('daily play counts'). It distinguishes from sibling tools like 'tautulli_plays_by_hour' and 'tautulli_most_watched' by specifying the time granularity ('daily') and breakdown ('by stream type').

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 no guidance on when to use this tool versus alternatives such as 'tautulli_plays_by_hour', 'tautulli_plays_by_day_of_week', or 'tautulli_most_watched'. It also lacks prerequisites or limitations like minimum days or data availability.

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