Raw Clockify API request

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds the meaningful behavioral constraint that the tool respects read-only mode and the workspace lock. This tells the agent that mutation attempts may be blocked even though the schema allows POST/PUT/DELETE. It does not disclose auth, rate limits, or response format, but these are less critical given the read-only annotation.

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 three short sentences, front-loaded with purpose, and contains no filler. Each sentence contributes either scope, routing guidance, or a constraint, making it easy to parse quickly.

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 deliberately generic raw API tool, the description covers purpose, usage conditions, path conventions, host selection, and behavioral constraints. It does not describe expected response format, but no output schema is present and the raw request nature makes it somewhat inferable; a bit more detail on return handling would have made it 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?

Schema coverage is 100%, and the schema already thoroughly describes all five parameters, including path examples and the meaning of the surface enum. The description's path and surface clarifications largely restate schema information, so it adds no significant parameter-level meaning beyond what is already structured.

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 identifies this as a catch-all for any Clockify endpoint that lacks a dedicated tool, which distinguishes it from the extensive list of sibling tools. It also gives concrete framing around API-relative paths and host surfaces, making the tool's scope and resource type 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 phrase 'any Clockify endpoint that has no dedicated tool' is an explicit when-to-use instruction, directly steering the agent away from sibling tools that cover specific endpoints. It also adds routing guidance for choosing the reports or time-off surface, which is actionable context.

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