show_current_time_entry

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

No annotations are provided, so the description carries the behavioral burden. The phrase 'if any' discloses that the tool handles the case of no running entry, which is a useful detail. However, it does not explicitly state that the operation is read-only or describe any side effects, though the verb 'Show' implies safety. This provides some but not rich behavioral 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?

The description is a single, concise sentence of eight words. It is front-loaded with the action and resource, and every word contributes meaning. There is no redundancy or unnecessary detail.

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 tool with no output schema, the description fully explains the tool's behavior: it shows the currently running time entry, or explicitly handles the absence of one. Given the simplicity of the tool, this is sufficient for an agent to select and invoke it correctly.

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, giving it a baseline score of 4. The description does not need to add parameter semantics because there are none to explain, and the schema's 100% coverage confirms this.

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 uses a specific verb 'Show' and identifies a precise resource: 'the currently running time entry.' The qualifier 'if any' adds nuance. This clearly distinguishes it from sibling tools like start_tracking, stop_tracking, and list_workspaces, which serve different purposes.

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?

The description states what the tool does but provides no guidance on when to use it versus alternatives. There is no mention of checking status before starting/stopping a timer, nor any exclusions or context for how it fits into a workflow. The usage is left entirely to inference.

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