List Clockify tasks

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the core action without mentioning return format, pagination, permissions, or side effects. The GitHub labels note is semantic, not behavioral, leaving the agent without insights into potential edge cases or expectations.

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?

A single sentence with the action front-loaded and a relevant parenthetical hint. Every word earns its place, with no redundancy or filler.

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?

With no output schema and no annotations, the description should ideally mention return structure or behavioral nuances. The GitHub labels hint provides some domain context but does not complete the picture for an agent deciding whether to invoke the tool. It is minimally viable for a simple list operation but leaves gaps.

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 input schema already provides clear descriptions for both parameters ('Clockify project ID' and 'Workspace ID override'), achieving 100% coverage. The description's phrase 'for a project' redundantly aligns with project_id but adds no new parameter details. Baseline of 3 is appropriate since the schema does the heavy lifting.

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?

Description clearly states the verb 'Lists', resource 'tasks', and scope 'for a project', making the tool's purpose unambiguous. It differentiates from sibling tools like clockify_list_tags or clockify_list_projects by focusing on tasks tied to a project. The parenthetical about GitHub labels adds domain context but does not confuse the core purpose.

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 context for when the tool would be useful (listing project tasks, mapping to GitHub labels) but does not explicitly state when to prefer it over alternatives such as clockify_ensure_task or clockify_list_projects. There is no exclusionary guidance, so usage is implied rather than clearly directed.

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