Ensure Clockify project

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

With no annotations, the description explicitly discloses that the tool may create a project, a mutating behavior. It also explains the default name resolution. However, it doesn't disclose details like idempotency guarantees, potential for multiple matches, or permission requirements. The description adds some behavioral context beyond the schema but is thin overall.

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 short sentences with no filler. The key action and default behavior are front-loaded, making it easy to parse.

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?

The description covers the main behavior and defaulting but lacks return-value information and edge-case handling. Given the tool's simplicity and absence of annotations, it is minimally adequate but not fully complete.

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 describes both parameters with 100% coverage. The description adds extra semantic value for the name parameter by specifying the default source (.clockify.yml/repo folder). This is useful beyond the schema's generic description.

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 action: 'Finds a project by name or creates it.' This distinguishes it from sibling tools like clockify_list_projects (read-only) and clockify_ensure_task (for tasks). The 'ensure' semantics are explicit and unambiguous.

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 doesn't explicitly state when to choose this over alternatives, but the 'finds or creates' behavior implies it's for guaranteeing a project exists. It mentions defaulting from .clockify.yml/folder, giving context for typical usage, but lacks explicit exclusions or alternative recommendations.

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