get_manual_time_entries_for_task

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

With no annotations, the description carries the full behavioral burden. 'Get' implies a read, but nothing is said about return format, pagination, permissions, or how manual entries differ from non-manual ones – a significant gap for a no-annotation tool.

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 compact sentence with no waste and the scope ('on a specific task') placed up front. Efficient, though it errs toward under-specification rather than true crispness.

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 tool with no annotations, no output schema, and one of two parameters undocumented, the description does too little. It never clarifies the manual-vs-regular time-entry distinction or the return shape, leaving meaningful gaps.

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 coverage is only 50%: board_name is documented in the schema, but task_id has no description anywhere. The phrase 'on a specific task' vaguely gestures at task_id but adds no format or meaning beyond the parameter name, so the description fails to compensate for the coverage gap.

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 ('Get') and resource ('manual time entries') scoped to 'a specific task', so the operation is clear. However it does not distinguish itself from the close sibling get_time_entries_for_task, leaving the 'manual' qualifier as the only differentiator an agent must infer.

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 when-to-use guidance, no prerequisites, and no mention of alternatives such as get_time_entries_for_task, get_time_entries_for_board, or add_manual_time_entry. The agent gets no routing help among the closely related time-entry siblings.

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