Ticket triage

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

The description adds a meaningful behavioral detail beyond annotations: 'Costs credits from the account wallet.' This is useful for an agent deciding whether to invoke the tool. Annotations already indicate readOnlyHint=false and destructiveHint=false, and the description does not contradict them.

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, dense sentence that front-loads the core purpose and output list, then adds the cost warning. Every element earns its place with no filler or repetition.

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, the description does a good job enumerating the expected outputs, which an agent needs to understand the return value. It also flags the credit cost. It could be slightly more complete by mentioning that teams and categories are optional inputs or by noting how the suggested first response is generated, but the overall context is sufficient for a triage tool.

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 description coverage is 100%, so the baseline is 3. The description does not elaborate on the teams or categories parameters beyond what the schema already provides, but it does clarify that the tool outputs a category and team, which indirectly hints at the purpose of those parameters.

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 identifies the resource (support ticket) and the transformation it performs, enumerating concrete outputs: priority, category, team, sentiment, SLA risk, and suggested first response. It is distinct from siblings like parserail_sentiment or parserail_classify because it combines multiple triage outputs in one call, though it does not explicitly name any sibling as an alternative.

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 phrase 'A support ticket → ...' implies the tool is meant for triaging support tickets, which gives some context. However, there is no explicit guidance on when to use this tool versus the many sibling tools that overlap with sentiment, categorization, or classification, and no when-not-to-use guidance.

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