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 mentions 'Auto-detects workspace' which adds useful context about default behavior, but fails to describe critical aspects like whether this tool requires authentication, what happens if a timer is already running, error conditions, or the response format. For a mutation tool with zero annotation coverage, this is insufficient.

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 with just two sentences that both add value. The first sentence states the core purpose, and the second provides important contextual guidance about workspace auto-detection and project ID sourcing. There's no wasted language or redundancy.

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 mutation tool with 4 parameters, no annotations, and no output schema, the description is incomplete. While concise, it lacks information about authentication requirements, error handling, what the tool returns, whether it's idempotent, or how it interacts with other timer-related tools. The agent would need to guess about important behavioral aspects.

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 100%, so the schema already documents all 4 parameters thoroughly. The description doesn't add any parameter-specific information beyond what's in the schema descriptions, maintaining the baseline score. It doesn't explain parameter relationships or provide usage examples.

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 action ('Start a timer') and resource ('timer'), making the purpose immediately understandable. It distinguishes from sibling tools like 'stop_timer' or 'get_running_timer' by specifying the starting action, though it doesn't explicitly contrast with all alternatives like 'log_time'.

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 some usage context by mentioning 'Auto-detects workspace' and referring to 'get_projects for project IDs', which implies when to use related tools. However, it lacks explicit guidance on when to choose this tool over alternatives like 'log_time' or 'create_time_entry', and doesn't specify prerequisites or exclusions.

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