cleanuparr_get_event_timeline

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

The readOnlyHint annotation already indicates a safe read operation, and the description's 'Get' aligns with that. However, the description adds no extra behavioral context beyond what annotations provide, such as what 'timeline buckets' represent or any aggregation behavior.

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, front-loaded with the verb and resource. Every word earns its place; there is no fluff or unnecessary detail.

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?

For a tool with one optional parameter, an output schema, and a readOnlyHint, the description is sufficient. It clearly states the core action and the parameter's role, though it does not elaborate on 'timeline buckets'—a gap partially filled by the output schema.

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 schema has zero description coverage, so the description must compensate. 'For the requested number of hours' clarifies the meaning of the 'hours' parameter, but it does not explain how hours affect the buckets or what the buckets contain. Minimal added value beyond the schema's existence.

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 uses the specific verb 'Get' and identifies the resource as 'event timeline buckets' with a qualifier for the time range. It is clear what the tool does but does not differentiate from siblings like cleanuparr_get_event or cleanuparr_get_stats_timeline, and 'buckets' remains undefined.

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 gives no guidance on when to use this tool versus related event/timeline tools. It does not mention alternatives, prerequisites, or typical use cases. The only contextual hint is the 'requested number of hours,' which is more about the parameter than usage.

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