get_ticket_categories

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

Annotations already declare readOnlyHint=true, which is consistent with the 'List' verb. The description adds no additional behavioral context beyond the read-only nature, such as pagination, sorting, or scope of results. Since the annotation covers the safety profile, a score of 3 is appropriate – the description is consistent but adds minimal extra value.

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, precise sentence with no filler. It conveys exactly what the tool does and nothing more, which is ideal for a zero-parameter read operation.

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 list tool with no parameters and no output schema, the description provides sufficient information: it lists support ticket categories and priorities. It does not specify whether all categories are returned or if there is any filtering, but given the lack of parameters, this is likely all categories. The description is adequate for an agent to invoke correctly.

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 tool has zero parameters, so per the rubric the baseline is 4. The description does not need to elaborate on parameters. The empty schema covers 100% of parameters, and the description's mention of 'categories and priorities' describes the output, not inputs.

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 action ('List') and the resource ('support ticket categories and priorities'), making the purpose obvious. It does not explicitly distinguish from siblings like get_ticket or get_outage_tickets, but the resource is specific enough that an agent can infer it is for categories/priorities, not individual tickets or outage tickets.

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?

No guidance is provided on when to use this tool versus alternatives. It does not mention that get_ticket retrieves a single ticket or that get_outage_tickets lists outage-specific tickets, leaving the agent to infer the appropriate context.

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