Today's deposits

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

With no annotations, the description carries the full burden of behavioral disclosure. It states what is included (completed focus sessions, tasks, minutes) but does not disclose if this is a read-only operation, how recent the data is, whether it includes incomplete sessions, or any side effects. As a query-like tool, more context about filtering or time boundaries is needed.

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 sentence that immediately states the core purpose. It is concise and free of fluff, though it could add a bit more detail about the output or usage without becoming verbose.

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 no parameters and no output schema, the description gives the essential idea but remains thin. It does not explain what 'deposits' means beyond sessions, nor does it note how this differs from dwt_stats or dwt_status. Given the sibling context, an agent would benefit from a sentence clarifying when this is the right choice.

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 tool has zero parameters, so there are no parameter semantics to clarify. The description's reference to 'today's' provides context that a date parameter is not needed, making the lack of parameters self-explanatory.

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 tool's output as 'today's ledger statement' listing completed focus sessions with their tasks and minutes. It distinguishes the tool by focusing on today's deposits specifically, which sets it apart from sibling tools like dwt_stats or dwt_status, though it lacks an explicit verb like 'get' or 'list'.

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 provided on when to use this tool versus alternatives. The description does not mention any conditions for use, exclusions, or reference sibling tools, leaving the agent to infer from the name alone.

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