time_entry_create

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

With no annotations, the description carries full burden for behavioral disclosure. It mostly restates schema requirements and does not explain edge cases (e.g., what happens if both duration and end_time are provided, permission requirements, or the return value). The only added hint is 'manual' and the 'or' relationship between duration/end_time.

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 sentences, front-loaded with purpose, no redundant filler. Every sentence contributes meaning.

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?

The description covers the core action and required fields but omits return value behavior (no output schema) and any interaction with optional parameters like tags or billable. It is adequate for a straightforward create but lacks depth for a tool with 8 parameters and no annotations.

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%, providing baseline of 3. The description adds value by clarifying the optional duration/end_time relationship, suggesting they are alternatives rather than independent optional fields, which is not evident from the schema alone.

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 with a specific verb ('Create'), resource ('manual time entry'), and object ('task'). It also distinguishes from siblings by emphasizing 'manual', separating it from time_tracking_start/stop.

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: 'manual' time entry suggests comparing to timer-based entry, and the required fields give a clear prerequisite. However, it does not explicitly name alternatives or when-not-to-use cases, so it falls short of a perfect score.

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