clickup_time_history

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It clearly indicates this is a read-only fetch operation (not destructive) and specifies the return format ('array of history event objects'). However, it doesn't mention potential limitations like rate limits, authentication requirements, pagination behavior, or whether historical data might be truncated.

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 efficiently structured in two sentences: the first explains what the tool does with specific details, the second states its purpose and return format. Every word earns its place with zero redundant information. It's appropriately sized for a straightforward fetch operation.

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 read-only fetch tool with 2 well-documented parameters and no output schema, the description provides adequate context. It explains what data is returned and the tool's auditing purpose. However, without annotations or output schema, it could benefit from more behavioral details like response structure examples or access requirements to be 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 description coverage is 100%, so the schema already documents both parameters thoroughly. The description doesn't add any parameter-specific information beyond what's in the schema descriptions. It mentions the timer_id parameter indirectly by referring to 'time tracking entry' but provides no additional syntax, format, or usage details for either parameter.

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 specific action ('fetch the audit history of edits'), resource ('time tracking entry'), and scope ('every start/duration/description/billable change, the user who made it, and when'). It distinguishes itself from sibling tools like clickup_time_list or clickup_time_get by focusing on historical audit data rather than current time entries.

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 implies usage context ('useful for auditing') but doesn't explicitly state when to use this tool versus alternatives. It doesn't mention prerequisites like needing a timer_id from clickup_time_list or clarify if this is for compliance versus debugging purposes. No explicit exclusions or comparisons to similar audit tools are provided.

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