Clockify MCP Server

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the tool 'checks' status and 'auto-detects,' which implies a read-only, non-destructive operation. However, it doesn't disclose important behavioral traits: what specific data is returned (e.g., timer details, elapsed time), error conditions (e.g., what happens if no timer is running), or performance characteristics. The description is minimal and leaves key behavioral aspects unspecified.

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 extremely concise (two short sentences) with zero wasted words. The first sentence states the core purpose, and the second adds important behavioral context. Every element earns its place, and the information is front-loaded with the primary function stated first.

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 the tool's low complexity (single optional parameter, no output schema, no annotations), the description is minimally adequate. It covers the basic purpose and auto-detection behavior but leaves significant gaps: no information about return values (critical for a status check tool), no error handling details, and no context about how this integrates with timer control tools. For a status-checking tool, the description should ideally specify what information is returned.

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 description adds meaningful context beyond the input schema. While the schema has 100% coverage for the single parameter (workspaceId with default behavior documented), the description's 'Auto-detects workspace/user' provides crucial semantic context about automatic detection logic that isn't captured in the schema's parameter description. This compensates for the schema's technical focus with practical usage information.

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's purpose: 'Check if timer is running' specifies the verb (check) and resource (timer status). It distinguishes from siblings like start_timer/stop_timer by focusing on status checking rather than control. However, it doesn't explicitly differentiate from other read operations like get_time_entries.

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 provides implied usage context through 'Auto-detects workspace/user,' suggesting it's for checking current timer status without manual identification. However, it lacks explicit guidance on when to use this versus alternatives like get_time_entries (which might show timer data) or stop_current_timer (which requires knowing if a timer is running). No when-not-to-use or prerequisite information is provided.

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