rm_create_time_entry

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

Annotations already indicate readOnlyHint=false and destructiveHint=false, so the description adds no extra behavioral context such as idempotency, duplicate handling, required permissions, or side effects beyond creating a record. The only added detail, the date format, is parameter semantics rather than behavioral disclosure.

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, front-loaded sentence with no filler or redundant phrasing. It is appropriately concise for the core action, even though the brevity leaves other dimensions underserved.

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?

With 8 parameters, 4 required, zero schema descriptions, and no guidance about defaults or relationships between fields, this one-sentence description is insufficient for an agent to invoke the tool correctly in non-trivial cases. The output schema exists, but parameter semantics remain largely unexplained.

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 0%, so the description must compensate, but it only explains the date format. It provides no additional meaning for hours, is_billable, phase_id, notes, custom_field_values, or the ID parameters, leaving the agent to infer most semantics from property names 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 states a specific verb ('Create'), a specific resource ('a new time entry'), and the target context ('for a user on a project'), which clearly distinguishes it from sibling tools like rm_update_time_entry, rm_get_time_entry, and rm_delete_time_entry. The date format hint is a useful addition.

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 rm_fill_weekly_timesheet or rm_update_time_entry. There are no prerequisites, exclusions, or conditions that would help an agent decide between creating a single entry and using a bulk timesheet tool.

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