clockify_request

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

With no annotations, the description carries the full behavioral burden, but it only states the path prefix requirement. It omits critical traits such as authentication needs, rate limits, error handling, side effects of mutating methods, and how the generic request is actually performed.

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 tightly worded sentences with zero waste; the purpose is front-loaded and the path constraint and usage guidance follow immediately. Nothing is repeated or padded.

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 low-level, multi-method API passthrough with no annotations and no output schema, the description is too thin. It does not explain how to choose methods, handle responses, authenticate, or deal with errors, leaving an agent underprepared for correct invocation beyond the path prefix.

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 75%, so the schema already documents body, path, and query. The description adds a useful path constraint ('must start with /v1/') but says nothing about method selection, body construction, or query composition, leaving the baseline 3 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?

States a clear resource (any documented Clockify v1 endpoint) and the tool's role as low-level access, distinguishing it from curated siblings by saying it is for endpoints not covered by them. However, the verb 'access' is somewhat generic and it does not name specific sibling tools or enumerate what 'curated tools' means.

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?

Explicitly says to use this for endpoints not covered by curated tools, which gives clear context for choosing it over the listed sibling tools. It adds the path constraint but stops short of stating exclusions or prerequisites like authentication.

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