wetrack_get_ticket_comments

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

With no annotations, the description carries the behavioral burden. It communicates a read-only operation, complete scope ('all comments'), and ordering, but it does not disclose pagination, authentication requirements, or behavior when a ticket has no comments or an invalid UUID.

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 compact, front-loads the main behavior and ordering, and includes only the essential parameter detail. Every sentence contributes value, with no redundant 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?

For a single-parameter read-only ticket sub-resource with an output schema available, the description supplies the necessary invocation information. It could be slightly stronger with explicit guidance about pagination or the relationship to get_ticket_history, but nothing essential is missing for a basic call.

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 provides only the parameter name and type, with no description, so the tool description compensates by defining ticket_id as 'The ticket UUID.' This adds genuinely useful format information beyond the schema.

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 action and resource: 'Get all comments on a ticket' and adds the ordering guarantee 'in chronological order.' This clearly separates it from sibling tools like wetrack_get_ticket_history or wetrack_add_ticket_comment.

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 intended use is implied by the description: call this when you need the comment thread for a ticket. However, it does not explicitly mention alternatives or exclusions, such as when wetrack_get_ticket_history might be more appropriate.

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