dawarich_get_timeline

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

No annotations are provided, so the description alone must disclose behavior. It only says 'Get', implying a read operation, but omits details like output grouping, pagination, timezone handling, or format constraints. Minimal behavioral transparency.

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?

Single sentence, no filler, and front-loaded with the verb and resource. Efficient for what it covers.

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 tool's role among many sibling context tools and the lack of annotation and schema descriptions, the description leaves important gaps in when and how to invoke it. The output schema may help, but the description does not bridge usage semantics.

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 descriptions cover 0% of parameters, and the description does not name start_at, end_at, or distance_unit explicitly. 'Date range' loosely maps to date params but distance_unit is entirely unexplained.

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 identifies the action ('Get') and resource ('day-by-day Dawarich timeline context') with a date-range scope. It is specific enough to distinguish from sibling tools focused on map context, stats, or point search, though 'context' remains somewhat abstract.

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?

No guidance is given on when to choose this tool over siblings like dawarich_get_map_context or dawarich_get_stats, or on prerequisites. The phrase 'for a date range' gives minimal context but no comparative guidance.

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