list_organization_ticket_groups

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

No annotations are provided, so the description carries the full behavioral disclosure burden. 'List' conveys a read-only operation, but the description does not mention pagination, even though the continuation parameter exists, nor any filtering, ordering, or scoping nuances.

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?

A single, efficient sentence that front-loads the action and scope. It is not wasteful, though it is terse enough to leave important details to the schema and other sources.

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 read-only list with an output schema, the description is minimally adequate, but it lacks guidance on continuation-based pagination and does not clarify how this relates to sibling ticket-group tools. It is not incomplete enough to be unusable, but it leaves gaps.

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 0%, so the description must compensate for the undocumented parameters. It only hints at organization_id via 'under an organization' and says nothing about continuation, leaving the agent to guess its purpose.

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 verb (List), resource (ticket groups), and scope (under an organization). This clearly distinguishes it from sibling tools like get_ticket_group (single fetch) and create/update/delete_ticket_group.

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 the tool is used with an organization_id, but it gives no explicit when-to-use guidance and does not name alternatives or exclusions. The context is clear enough for a simple list operation, but it does not help an agent choose between this and related ticket-group or list_organization_* tools.

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