weeek_task_timer

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It reveals this is a mutating tool (start/stop) but does not state whether calling 'stop' on a non-running timer is harmless, whether 'start' on an already-running timer resets or ignores, what side effects occur (e.g., creating a time entry), or whether permissions are required.

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, concise sentence with zero waste. It is appropriately front-loaded and immediately conveys the core function.

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?

The tool has no annotations and no output schema, and there is a closely-related sibling (weeek_manage_time_entry) creating ambiguity. For a mutating tool, the description should clarify behavior on edge cases (double-start, double-stop), whether timers are per-user or per-task, and how it differs from the time entry management tool. This is meaningfully incomplete.

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 0%, so the description must compensate, but it provides no parameter documentation beyond what the schema already contains. The two parameters (task_id, action) are self-explanatory from their names, and the enum makes 'action' clear, so the baseline is reasonable, but no additional semantics are added to justify a higher score.

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 'Start or stop the running timer on a task' clearly states the verb (start/stop) and resource (task timer), matching the action and task_id parameters. However, it doesn't meaningfully differentiate from the related weeek_manage_time_entry sibling, which may be the more appropriate tool for some timer operations.

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 guidance on when to use this tool versus the closely-related weeek_manage_time_entry, nor are exclusions or prerequisites given. The description implies usage context ('running timer on a task') but does not state whether timers time-track against a project or whether starting requires an existing time entry.

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