summarize_dayProduces a daily time-tracking summary so you can review wall and attention minutes per area, classifications, levers, sessions, gaps, overlaps, and overrides.
Full summary of a day: wall and attention minutes per area, classification and lever, sessions, gaps, overlaps, overrides.
| Name | Required | Description | Default |
|---|---|---|---|
| date | No | YYYY-MM-DD in the user's timezone |
Changes observed during successful MCP inspections.
v0.4.2Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description goes beyond that by enumerating the returned payload (minutes per area, classification, lever, sessions, gaps, overlaps, overrides), which is valuable since no output schema exists. It does not mention cost, pagination, or behavior for days with no data.
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?
A single front-loaded sentence with a compact enumeration; every token carries content. The colon-list style is dense but readable, with no filler or repetition.
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 carries the burden of describing the response and does so at a field-group level, which is enough for an agent to decide whether to call it. The only gap is the omitted-parameter default and empty-day behavior.
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 coverage is 100% and the single 'date' parameter is fully documented there (YYYY-MM-DD, user timezone). The description adds nothing about the parameter, and since it is optional (0 required) it does not explain what happens when it is omitted (presumably today). Baseline 3 applies.
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?
Names a specific verb+resource ('summarize day') and enumerates exactly what the summary contains (wall/attention minutes per area, classification, lever, sessions, gaps, overlaps, overrides), so an agent knows this is a read of aggregated daily data. It does not explicitly distinguish itself from the sibling summarize_week, but the day/week scope split is inferable.
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?
There is no when-to-use guidance, no prerequisites, and no mention of the sibling summarize_week as an alternative for multi-day rollups. Usage is only weakly implied by the resource name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.