add_manual_time_entry

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

No annotations are provided, so the description carries the full behavioral burden. It states the core action but omits whether this requires specific permissions, whether timestamps must be in the past, whether the board must be configured, and what constraints apply. For a mutation tool without annotations, this is a notable gap.

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 efficient sentence that front-loads the core action. It is not padded, but it is also under-specified, which is a mild weakness rather than a conciseness problem.

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 7-parameter mutation tool with no annotations, no output schema, and only 57% schema description coverage, the description is too thin. It should address required board configuration, usage constraints, and the meaning of undocumented parameters to be complete enough for reliable invocation.

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 57%, leaving several parameters (userId, task_id, labelNames, comment) without schema descriptions. The description only clarifies the timestamp format and the manual-entry nature, not the meaning of the undocumented parameters. Baseline 3 is appropriate given partial schema coverage.

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: 'Add a manual time entry to a task', reinforced by the ISO 8601 timestamp requirement. It clearly distinguishes the tool from read siblings like get_manual_time_entries_for_task and get_time_entries_for_task, though it doesn't explicitly name them.

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 given on when to use this tool versus alternatives such as get_time_entries_for_task or get_manual_time_entries_for_task. It also omits any exclusions or preconditions (e.g., whether the task must belong to the given board, whether overlapping entries are allowed).

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