Current focus session and today's total

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

No annotations are provided, so the description carries the burden. It discloses what is returned (active session details if any, and today's total), including the conditional 'if any' and the device ownership detail. It implicitly signals a read-only operation via 'Show', which is useful behavioral context.

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 with no redundancy. The main output is stated first, followed by a clear directive on when to call it. Every sentence earns its place.

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 zero-parameter status tool, the description fully covers what an agent needs to know: what it returns, the conditional nature of the active session, and the recommendation to call it first. No output schema exists, but the described return values are sufficient.

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 the schema provides no parameter details. The description appropriately focuses on behavior rather than parameters, matching the baseline for parameter-less tools.

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?

Description clearly states the tool shows the active Deep Work Timer session (with task, time remaining, device) and today's total focus time. It uses a specific verb ('Show') and resource, distinguishing it from sibling tools like dwt_stats or dwt_log_session.

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?

Explicitly instructs to call this tool first before starting or logging anything, providing clear usage context. However, it does not explicitly mention when not to use it or name alternative tools for other scenarios, though the instruction is sufficient for primary use.

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