Get Dawarich timeline

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

Annotations declare readOnlyHint=true and destructiveHint=false, and the description adds the important behavioral constraint of a maximum 31-day date range, which affects invocation. No additional side effects are mentioned, but the safety profile is already covered by 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?

Two sentences, each with a clear purpose: the first states the functionality, the second states a constraint. No fluff or repetition of schema 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 no output schema, the description provides some return content ('visits, tracks, and photos') and implies a daily structure, but it does not clarify pagination, response format, or how this differs from closely related sibling tools. The 31-day limit is helpful, but the description is relatively sparse for a tool with multiple siblings.

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 100%, with both start_at and end_at having descriptions in the schema. The description adds the 31-day range constraint, which indirectly informs parameter usage, but adds no syntax or format details beyond the schema.

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 'Returns' and identifies the resource as 'day-by-day timeline data' with content including 'visits, tracks, and photos'. This distinguishes it from sibling tools like dawarich_get_stats or dawarich_list_points, which serve different purposes.

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 use for timeline retrieval but does not explicitly name alternatives or state when not to use it. The maximum date range of 31 days provides a clear constraint, but there is no guidance on choosing between this and sibling tools.

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