wetrack_get_ticket_history

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

With no annotations, the description carries the full behavioral burden, and it does disclose the key behavior: the returned data is the full audit/changelog including every field change, the actor, and the timestamp. It could add more about ordering, pagination, or error behavior, but the core semantics of a read-only history lookup are clearly conveyed.

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 two sentences plus a one-line Args section, with no filler. The main behavior is front-loaded in the first sentence, and the parameter note is immediately relevant.

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 simple one-parameter read-only getter with no nested objects and an output schema available, the description is complete enough for an agent to call it correctly. It states the input, the resource, and the nature of the returned history.

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 0%, so the description must compensate, and it does by identifying ticket_id as 'The ticket UUID' rather than just repeating the schema title. This is sufficient for a single-parameter tool, though it does not specify UUID format or how to find the ID.

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 and resource ('Get the full audit history/changelog for a ticket') and defines the scope by saying it shows every field change with who made it and when. This clearly distinguishes it from sibling ticket tools like get_ticket_comments or get_ticket_watchers.

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 clearly implies use when a ticket's change history is needed, but it never states when to prefer this tool over alternatives or when not to use it. There is no explicit mention of sibling tools such as wetrack_get_ticket for current state or wetrack_get_ticket_comments for comments.

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