Time Create Time Entry

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

Annotations already declare readOnlyHint=false, idempotentHint=false and destructiveHint=false, so the safety profile is covered structurally. The description adds nothing behavioral on top: it does not warn that repeated calls create duplicate entries (non-idempotent), does not state permission/auth requirements, and does not say what happens on validation failure.

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?

A single efficient sentence with the core operation front-loaded and the date format parenthetically appended. No wasted words, though it is arguably too terse for an 8-parameter mutation tool.

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?

An output schema exists so return values need not be explained, but for a non-idempotent write tool with 8 parameters at 0% schema coverage and no usage guidance, the description leaves major gaps. An agent cannot tell how the optional billing/phase/custom-field parameters affect the created entry.

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% across 8 parameters, so the description carries the full burden and mostly fails. It names user, project and date (with a YYYY-MM-DD format hint), but says nothing about hours, notes, phase_id, is_billable (which defaults to true and has billing impact), or custom_field_values.

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?

States a specific verb and resource ("Create a new time entry") plus the linking entities (user, project), so the operation is unambiguous. It does not distinguish itself from the many sibling tools in the time family (update/delete/list time entries), so it stops short of a 5.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives such as time_update_time_entry or time_fill_weekly_timesheet. The agent must infer usage entirely from the name.

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