clickup_time_stop

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

No annotations are provided, so the description carries full burden. It states the action ('Stop') but doesn't disclose behavioral traits such as whether this requires specific permissions, what happens if no time entry is running (error vs. no-op), or the response format. For a mutation tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 a single, clear sentence with zero waste. It's front-loaded with the core action and target, making it easy to parse. Every word earns its place by directly conveying the tool's purpose without redundancy.

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 the tool's mutation nature (stopping time tracking) and lack of annotations or output schema, the description is incomplete. It doesn't cover error conditions, permissions, or what the tool returns, leaving the agent with insufficient context for reliable invocation. A more detailed description would be needed to compensate for the missing structured data.

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%, with the single parameter 'team_id' fully documented in the schema. The description adds no parameter information beyond what the schema provides, so it meets the baseline of 3 where the schema does the heavy lifting. No additional semantics are contributed.

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 action ('Stop') and the target ('currently running time tracking entry'), providing a specific verb+resource combination. It distinguishes from sibling tools like 'clickup_time_start' and 'clickup_time_update' by focusing on stopping rather than starting or modifying time entries. However, it doesn't explicitly differentiate from all time-related siblings like 'clickup_time_delete' or 'clickup_time_current', which prevents a perfect score.

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 no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., that a time entry must be running), exclusions, or comparisons to siblings like 'clickup_time_current' (which might check status) or 'clickup_time_update' (which might modify without stopping). The agent must infer usage from the tool name alone.

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