Get task activity

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

The annotations already declare readOnlyHint: true, so the safety profile is covered. The description adds meaningful behavioral details beyond the annotation: it discloses the output ordering ('newest first') and the specific event categories included ('status/priority/assignee/field changes, comments, worklogs'). It does not contradict the annotations, and the added context is useful but not exhaustive (e.g., no mention of pagination or access requirements).

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, information-dense sentence. It front-loads the core action ('Get the audit trail for a task') and immediately provides scope and ordering details. There is zero redundancy or 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?

The tool has one simple parameter and is a read-only operation. There is no output schema, so the description reasonably carries the burden of explaining what the tool returns. It enumerates the key dimensions ('who changed what and when') and the main event types, which is sufficient for an agent to decide whether to invoke it. The description is complete for the tool's simplicity.

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 input schema has 100% coverage: the only parameter, task_id, is described as 'Task UUID' with a uuid format. The description adds no further meaning to this parameter beyond the schema's own documentation. Since the schema already carries the full semantic load, a baseline score of 3 is appropriate.

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 clearly states the tool's purpose: 'Get the audit trail for a task: who changed what and when (status/priority/assignee/field changes, comments, worklogs), newest first.' It uses a specific verb ('get') and resource ('audit trail'), and it distinguishes itself from sibling tools like get_task_comments and get_task_worklogs by covering all change types. This makes it unmistakable what the tool does.

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 implies when to use this tool—when a comprehensive activity/audit trail is needed, as opposed to narrower tools for comments or worklogs. It names the included event types but does not explicitly call out alternatives or state when not to use it. The context is clear and the scope is well-defined, though explicit exclusion guidance is absent.

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