update_time_entry

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

Annotations already provide idempotentHint true, readOnlyHint false, and destructiveHint false. The description adds the 'Update' verb which is consistent but does not disclose any additional behavioral traits such as authorization requirements, rate limits, or side effects. Given the annotations cover the safety profile, the description does not add significant value beyond stating the obvious.

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 extremely concise with only two sentences, both front-loaded with the purpose and a key usage note. No unnecessary words, every sentence earns its place.

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 there is no output schema and 7 parameters, the description lacks information about return values, error handling, or success indicators. It also does not mention any related sibling tools for reference. While the partial update hint is useful, the description feels incomplete for a mutation tool.

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?

While all parameters have descriptions in the schema (100% coverage), the description adds the important semantic hint that only changed fields need to be provided, emphasizing the partial update behavior. This goes beyond the schema's basic field descriptions.

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 verb 'Update' and the resource 'time entry' along with the platform 'Productive.io'. It distinguishes itself from sibling tools like create_time_entry and delete_time_entry by specifying that it modifies an existing 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?

The description explicitly says 'Only provide the fields you want to change', which indicates a partial update pattern. However, it does not mention when to use this tool versus alternatives like create_time_entry or delete_time_entry, nor does it specify any prerequisites or context.

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