clockodo_update_entry

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

Annotations already convey non-readonly and non-destructive behavior. The description adds valuable behavioral context by clarifying partial-update semantics and the customers_id/projects_id consistency rule, which is not inferable from the schema alone.

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 concise sentences with no filler. The core update semantics and the critical domain constraint are presented directly and efficiently.

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 partial-update semantics and a key invariant, which is good. However, with 9 parameters, sparse schema coverage, and no output schema, an agent still lacks critical formatting and return-value context to confidently invoke the tool in all cases.

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 only 11% (only duration is documented). The description adds almost no parameter-level meaning beyond the customers_id/projects_id relationship, leaving most parameters such as time_since, time_until, services_id, and text unexplained.

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 'Updates an existing time entry,' which is a specific verb + resource. It is immediately distinguishable from sibling tools like create_entry, get_entry, and delete_entry.

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?

It explicitly instructs callers to pass only the fields to change and at least one field, which defines the intended invocation pattern. It does not name alternatives or state when not to use the tool, but the partial-update guidance is clear and useful.

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