List Clockify tasks

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

With no annotations provided, the description carries the full responsibility for behavioral disclosure. It reveals the user-scoped config_root requirement, which is useful, but it does not disclose return behavior, pagination, failure modes, or any side effects beyond listing. 'Lists tasks' is a safe read, so the gap is moderate rather than severe.

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 two sentences, front-loaded with the primary purpose, and reserves the second sentence for the only non-obvious usage nuance. There is no wasted wording.

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 simple read operation, complete param documentation in the schema, and the useful config_root clarification, the description is nearly complete. It could mention the GUI of the tool but lacks return-format or pagination details would be expected in the absence of an output schema.

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 project_id, config_root, and workspace_id in detail. The description adds no new parameter semantics beyond what the schema states, so baseline value 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 a specific action and resource: listing tasks for a project. It does not explicitly differentiate from sibling tools like clockify_ensure_task or clockify_list_tags, though the added 'often mapped 1:1 to GitHub labels' context gives useful semantic framing.

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 offers meaningful usage context by telling users to pass config_root as the repo's git toplevel when the MCP is user-scoped. However, it gives no guidance on when to choose this tool over related siblings or when workspace_id should be set.

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