create_time_entry

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions format requirements for 'started_at' but doesn't address critical aspects like authentication needs, error conditions, whether creation is idempotent, what happens on duplicate entries, or what the output contains. For a creation tool with zero annotation coverage, this leaves significant behavioral 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 appropriately concise with two sentences that get straight to the point. The first sentence states the core purpose, and the second provides the most critical parameter formatting information. No wasted words, though it could be slightly more structured.

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 that an output schema exists (which should document return values), the description doesn't need to explain outputs. However, for a creation tool with 6 parameters, 0% schema description coverage, and no annotations, the description provides only minimal context about two parameters and misses behavioral transparency aspects. It's minimally adequate but leaves significant gaps.

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?

The description adds minimal parameter semantics - it specifies the ISO8601 format for 'started_at' and clarifies 'duration_seconds' is in seconds. With 0% schema description coverage and 6 parameters, this provides some value but doesn't compensate for the majority of undocumented parameters (client_id, project_id, note, billable) that remain unexplained in both schema and description.

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 ('Create a time entry') and resource ('time entry'), making the purpose immediately understandable. However, it doesn't distinguish this tool from its sibling 'list_time_entries' beyond the obvious create vs. list distinction, missing an opportunity to clarify when to use each.

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 provided about when to use this tool versus alternatives like 'list_time_entries' or how it relates to other time-tracking operations. The description only states what the tool does, not when it should be invoked in context of the available sibling tools.

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