update_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 only states 'Update' without describing permissions, reversibility, side effects on related records, or whether partial updates are supported. For a mutation tool, this is insufficient.

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 sentence with no extraneous content. It efficiently conveys the core action and mentions key fields. However, it could benefit from a more structured format (e.g., listing all updatable fields) without becoming verbose.

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 8 parameters (1 required), no output schema, and no annotations, the description is too minimal. It does not clarify required inputs beyond the schema, expected behavior on success/failure, or common constraints (e.g., interaction between duration and start). An agent would lack sufficient context to use this tool reliably.

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 low (38%). The description lists 'description, duration, start, billable, tags' but does not explain their formats, constraints, or relationships. Key parameters like timer_id, team_id, and task_id are omitted. The description adds little meaning beyond what the schema already provides.

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 'Update a time entry' and lists some updatable fields, indicating the specific verb and resource. However, it does not differentiate from sibling tools like create_time_entry or stop_time_entry, missing an opportunity to clarify scope.

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 on when to use this tool versus alternatives such as create_time_entry, start_time_entry, or stop_time_entry. The description lacks context about prerequisites or appropriate scenarios.

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