gorelo_create_time_entry

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the agent knows this is a non-destructive write. The description adds nothing beyond that — no mention of validation failures (404 on unknown task/ticket), no side effects on billing or approvals, no note about what is returned.

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 terse sentence with zero waste, but it is undersized rather than appropriately sized — brevity here comes at the cost of missing information rather than from disciplined editing.

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?

For a nested 13-field mutation with no output schema, the description is thin, but the very rich schema carries most of the load. An agent could call it correctly from the schema alone, though it would learn nothing about outcomes or error behavior from the description.

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 100%, including the ticket/task exclusivity rule, enum values for BillableStatusId, and the 5000-character attachment limit, so baseline 3 applies. The description adds no parameter meaning of its own and its 'against a ticket' phrasing slightly conflicts with the documented TaskId alternative.

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 ('Logs time'), which distinguishes it from the list/get/update time-entry siblings. However, 'against a ticket' undersells the schema's TicketId-or-TaskId design, so the scope isn't fully accurate.

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 guidance on when to use this rather than gorelo_update_time_entry or gorelo_list_time_entries, and no mention of prerequisites such as needing a valid ticket/task, user, or work type. The agent must infer all usage context from the schema.

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