autotask_create_time_entry

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 explains the two creation modes (parented vs Regular Time) and mentions category requirements, which is helpful. However, it doesn't disclose important behavioral aspects like authentication requirements, rate limits, error conditions, or what happens on successful creation. For a creation tool with 12 parameters and no annotations, this leaves significant gaps.

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 perfectly concise - two sentences that efficiently cover both usage scenarios. The first sentence establishes the main purpose and alternatives, the second provides specific guidance for Regular Time. Every word earns its place with zero waste or 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 complexity (12 parameters, creation operation) and lack of both annotations and output schema, the description is somewhat incomplete. While it covers the two main usage patterns well, it doesn't address what happens after creation, error handling, or system constraints. For a creation tool with this many parameters and no structured safety/behavior annotations, more context would be helpful.

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 all 12 parameters thoroughly. The description adds some value by explaining the Regular Time use case and category requirement, but doesn't provide additional parameter semantics beyond what's already in the schema descriptions. This meets the baseline expectation when schema coverage is complete.

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 ('Create a time entry in Autotask') and distinguishes between two usage scenarios: tied to a ticket/task/project OR as 'Regular Time' with specific categories. This differentiates it from sibling tools like autotask_create_ticket or autotask_create_task by focusing specifically on time tracking.

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 explicit guidance on when to use each option: 'Can be tied to a ticket, task, or project, OR created as "Regular Time" (no parent) for meetings, admin work, etc.' It clearly defines the alternative use cases and specifies that Regular Time requires a category, giving clear when/when-not guidance.

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