Get Clockify user

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

There are no annotations, so the description carries the full burden. It clearly states a read-only behavior ('Returns...') and even names the included workspace IDs, but it does not describe authentication requirements, failure modes, or the behavioral implication of omitting config_root, which is optional per the schema.

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?

Two sentences, no filler. The high-level behavior comes first, followed by a focused parameter condition. Excellent front-loading and structure.

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 one-parameter getter, the description is mostly adequate and tells the agent what it returns. But it does not explain how to detect that the MCP is user-scoped, what happens if config_root is omitted, or how this relates to clockify_list_workspaces when both provide workspace IDs.

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 schema already documents config_root with 100% coverage and detailed resolution instructions. The description adds a meaningful condition—'when this MCP is user-scoped'—which explains when to supply the optional parameter. This goes slightly beyond the schema's baseline.

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 states a precise verb and resource: 'Returns the authenticated Clockify user, including active and default workspace IDs.' This is distinct among siblings, and the output is specified, so an agent can distinguish it from other clockify_* tools without opening schemas.

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 gives usage guidance for the parameter ('Pass config_root as that repo's git toplevel when this MCP is user-scoped'), but it does not explicitly tell an agent when to prefer this tool over alternatives such as clockify_list_workspaces or clockify_get_config. The tool's use is implied rather than explicitly stated.

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