create_time_entry

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The description only states what it does, not how it behaves: it doesn't state that a running timer may continue if stop is omitted, whether this can conflict with existing running timers, whether permissions beyond team membership are needed, or whether the `assignee` parameter lets one agent log time for another user. The schema hints at running-timer behavior via the stop parameter description, but the tool description itself is silent.

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 short sentence ('Log a time entry for a task'), which is concise. However, it is under-specified—there is no structure, no prerequisites, no team/workspace context, and no mention of the required team_id parameter or how this create operation relates to the broader timer lifecycle. Brevity alone isn't conciseness when meaningful info is absent.

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?

This is a mutation tool with 9 parameters, no annotations, and no output schema. The description provides essentially no information beyond the tool's name. For an API that exposes start_timer, stop_timer, get_running_timer, and update_time_entry as siblings, the description should clarify open-timer semantics, timer conflicts, and whether multiple entries can be open simultaneously. The description is inadequate for the complexity of this tool's domain.

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 78% (7 of 9 params have descriptions in the schema), so the schema carries most of the parameter documentation load. The description itself adds no parameter information. The core relationship—that start is required and stop vs duration are alternatives—is encoded in the schema but not explained in the description. Given the decent schema coverage, a baseline 3 is 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?

The description 'Log a time entry for a task' uses a clear verb+resource, establishing it as a write operation to create time entries. However, it doesn't distinguish itself from siblings like start_timer, stop_timer, or update_time_entry, which are related but serve different lifecycle purposes. The scope is understood but the tool-to-task relationship could be clearer.

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?

No guidance is given on when to use create_time_entry versus start_timer, update_time_entry, or stop_timer. The sibling set includes many timer-related tools, and the description provides no context on when a logged entry would be preferred over starting a running timer, nor excludes scenarios. The schema notes about running timers are the only implicit guidance.

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