get_time_status

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

Annotations absent, but description fully discloses read-only behavior, return content (state, tags, duration), and graceful handling of missing installation. No side effects implied; adequate transparency.

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?

Four concise, well-structured sentences. Every sentence adds value: purpose, return values, error handling, alternatives. No wasted words.

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 no parameters, existing output schema, and sibling tools, description fully covers behavior, output, edge case, and alternatives. No gaps.

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?

No parameters, schema coverage 100%. Description adds no param info (none needed) but exceeds baseline by clarifying zero-parameter nature implicitly. Baseline 4 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?

The description clearly states the tool checks if Timewarrior is tracking time (specific verb+resource), distinguishes itself from get_time_summary (historical aggregates) and start_task/stop_task (control). Read-only nature is explicit.

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 advises when to use alternatives: 'Use get_time_summary for historical aggregates. Use start_task / stop_task to control tracking via Taskwarrior hooks.' Also covers edge case (Timewarrior not installed) with non-error message.

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