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 provides some behavioral context about default parameter handling. However, it doesn't describe important aspects like whether this is a read-only operation, what format the list returns, if there's pagination, rate limits, or authentication requirements. For a tool with zero annotation coverage, this leaves significant gaps.

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 short sentences that communicate the core functionality and one key behavioral aspect. Every word earns its place, and the information is front-loaded with the primary purpose stated first. There's zero wasted verbiage 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?

Given this is a data retrieval tool with no annotations and no output schema, the description should do more to explain what the tool returns and any behavioral constraints. While the purpose is clear, important context is missing about the return format, pagination, error conditions, or how this fits within the broader system of sibling tools. The description is too minimal for a tool that presumably returns client data.

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 fully documents the single parameter. The description adds marginal value by mentioning 'Auto-detects workspace' which implies the workspaceId parameter defaults to the active workspace, but this is already stated in the schema description. The description doesn't provide additional parameter semantics beyond what's in the structured schema.

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 verb ('List') and resource ('clients'), making the purpose understandable. It doesn't explicitly distinguish from sibling tools like 'get_workspace_users' or 'get_tags', but the resource specificity ('clients') provides some differentiation. The mention of 'Auto-detects workspace' adds useful context about default behavior.

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?

No guidance is provided on when to use this tool versus alternatives. While it mentions auto-detection of workspace, it doesn't explain when you'd want to override this with the workspaceId parameter or how this tool relates to other get_* tools in the sibling list. The description lacks any 'when-to-use' or 'when-not-to-use' context.

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