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. While it mentions auto-detection of workspace (helpful context), it doesn't address important behavioral aspects: whether this creates new records or updates existing ones, what permissions are required, whether it's idempotent, what happens on failure, or what the response looks like. 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 - just two brief sentences that communicate essential information without any wasted words. It's front-loaded with the core purpose and includes only necessary additional context about workspace auto-detection.

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 6 parameters, no annotations, and no output schema, the description is incomplete. It doesn't explain what the tool returns, what happens on success/failure, or how it differs from similar sibling tools. The auto-detection hint is helpful but insufficient for proper contextual understanding.

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 6 parameters thoroughly. The description adds minimal value beyond the schema - it only reinforces the duration format example ('1h30m') which is already in the schema. No additional parameter semantics are provided, so baseline 3 is appropriate.

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: 'Log completed time with duration like "1h30m"'. It specifies the action (log), resource (time), and format requirement. However, it doesn't explicitly differentiate from sibling tools like 'create_time_entry' or 'update_time_entry', which appears to be a related functionality.

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 mentions 'Auto-detects workspace' which provides some context about default behavior, but offers no explicit guidance on when to use this tool versus alternatives like 'create_time_entry' or 'update_time_entry'. There's no mention of prerequisites, dependencies, or specific scenarios where this tool is preferred.

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