Focus Time Heatmap

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

With no annotations provided, the description carries the full burden of disclosure. It adds some useful behavioral context by stating that the heatmap shows daily focus totals including pomodoro and stopwatch time, but it does not disclose the response format, edge cases (e.g., empty days), or explicitly confirm read-only 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 two concise sentences, front-loaded with the main purpose and a secondary detail about what the heatmap includes. Every word serves a clear function, with no 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 tool's simplicity (two parameters, no output schema), the description covers the core behavior but leaves ambiguity about the exact return structure (e.g., is it an image or data array?) and lacks any limitations or usage caveats. It is adequate but not fully complete.

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 input schema already fully describes both parameters (from/to) with date format examples, achieving 100% coverage. The description merely reiterates the date-range concept without adding new semantic details such as inclusive/exclusive bounds or timezone handling.

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 a specific verb ('Get') and identifies the exact resource ('a heatmap of your focus/pomodoro time') with a date range scope. It clearly distinguishes this tool from siblings like productivity stats or task lists by focusing on the heatmap representation and daily focus totals.

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 alternative analytics tools such as ticktick_get_focus_distribution or ticktick_get_productivity_stats. It only states what the tool does without offering context on scenarios that favor this tool.

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