cleanuparr_get_stats_timeline

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

The readOnlyHint annotation already covers the read-only safety profile. The description adds useful context about available metrics and buckets, but does not disclose behaviors such as the effect of 'hours' or 'include_dry_run' parameters. No contradiction with annotations.

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, concise sentence that front-loads the core purpose and then lists relevant options. Every word adds information; no filler or redundancy.

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 output schema exists and annotations already declare read-only behavior, the description is mostly complete for a simple stats timeline. It covers the key dimensions (metrics and buckets) but could improve by explaining 'hours' and 'include_dry_run'. Overall adequate.

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 0%, so the description must compensate. It provides meaningful allowed values for 'metric' and 'bucket' parameters, but leaves 'hours' and 'include_dry_run' with no explanation. Partial compensation for the missing schema descriptions.

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 the tool's function: 'Get v2 metric timeline' with specific verbs and resource. It distinguishes itself from sibling tools by enumerating metrics (events, strikesIssued, recovered, removed, malwareBlocked) and buckets (hour, day, week, month), making its purpose unambiguous.

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 by listing metrics and buckets, but it does not explicitly state when to use this tool versus alternatives like get_event_timeline or get_stats. No exclusions or alternative recommendations are provided.

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