taiga_task_history

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

No annotations are provided, so the description carries the full burden. It states only that history is retrieved but does not disclose response format, ordering, pagination, or whether the history includes field changes versus comments. This lack of behavioral detail leaves the agent uncertain about the tool's output.

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 sentence with no filler, efficiently conveying the core function. It is front-loaded and optimally concise.

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?

With no output schema and no annotations, the description is too sparse. It does not explain what the returned history contains, how to interpret entries, or whether there are any limitations. For a history endpoint, the agent would need more context to effectively use the result.

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?

The schema covers 100% of parameters with the description 'task ID'. The tool description adds no additional meaning beyond the schema, but the high schema coverage meets the baseline for this dimension.

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 uses a specific verb 'Get' with a clear resource 'change history for a task'. It distinguishes from sibling history tools like taiga_userstory_history, taiga_issue_history, and taiga_wiki_history by explicitly limiting scope to tasks.

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 provides no guidance on when to use this tool versus alternatives. It does not mention that this returns a task's audit trail, contrast with taiga_tasks_get, or clarify that comments are handled elsewhere (e.g., taiga_task_comment_create).

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