create_time_entry

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

No annotations are provided, so the description must carry the full behavioral burden. It discloses that this creates a time entry and that spent_on defaults to today, but it does not describe permissions, side effects, reversibility, or what happens if both issue_id and project_id are supplied. For a mutation tool, this leaves significant gaps.

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 short, front-loaded with the purpose, and then structured as an argument list. Each sentence and bullet adds practical information, with no filler.

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. However, this is a six-parameter mutation tool with no annotations and 0% schema description coverage, and the description omits comments entirely, leaves project_id only implicit, and provides no usage or safety context. It is therefore not complete enough for correct invocation 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 0%, so the description must explain all six parameters. It usefully explains hours, issue_id, activity_id, and spent_on, and mentions project_id as an alternative to issue_id, but it completely omits the comments parameter and does not give project_id its own clear argument description.

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 and resource: recording work time linked to a ticket or project. This clearly matches create_time_entry and distinguishes it from sibling tools like update_time_entry and list_time_entries, though it does not explicitly contrast itself with those siblings.

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 gives the core purpose and notes that issue_id or project_id is required, but it does not state when to use this tool versus update_time_entry, delete_time_entry, or list_time_entries. The only procedural hint is to check activity IDs via list_metadata, which is parameter guidance rather than usage guidance.

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