log_time

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

With no annotations, the description carries the full disclosure burden. It does add one genuinely useful behavioral fact beyond the schema — that the entry is automatically assigned to the detected user — but says nothing about permissions, whether the entry is created immediately, or what the response contains.

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 short sentences, the key differentiator (manual vs. timer) front-loaded, and the auto-assignment side effect stated up front. No filler.

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?

Covers what it does and one side effect, but with no annotations and no output schema the description should say what a successful call returns (e.g., the created entry) and whether the issue must exist. It is adequate but leaves real gaps for a mutation tool.

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%, so hours format, date defaults, and the activity_id lookup route are already documented in the schema. The description adds no parameter meaning beyond that, so the baseline 3 applies.

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 specific verb ('log') and resource ('time entry for an issue') and explicitly contrasts with the timer-based path, which separates it from start_timer/stop_timer siblings. It does not distinguish itself from update_time_entry, but the create-vs-modify split is reasonably inferable from 'log'.

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 parenthetical 'without using start/stop timer' implies the condition for choosing this over the timer tools, but it never names them or states when-not to use it (e.g., correcting an existing entry should go to update_time_entry). Usage is implied rather than spelled out.

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