itglue_list_groups

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

No annotations present, so description must disclose behavioral traits. Only mentions filter support; does not address that it is a read-only operation, pagination behavior, authentication requirements, or rate limits. 'Supports filter[name]' is the sole behavioral hint.

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?

Two concise sentences with no unnecessary words. However, could be slightly restructured to front-load the core purpose more clearly; currently it's adequate but not exemplary.

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?

Given the tool has 4 parameters, nested objects, no output schema, and no annotations, the description is too brief. It omits details on pagination, default page size, expected response format, and differentiation from search tools. Incomplete for a list operation.

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 100% with detailed parameter descriptions. The description adds only 'Supports filter[name]', which echoes the schema. Baseline 3 is appropriate as description does not add significant new meaning 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?

Description clearly states it lists IT Glue user groups with 'List IT Glue user groups (RBAC)' and specifies a filter. Differentiates from sibling tools like itglue_get_group (single group) and itglue_list_users (users), though it could be more explicit about RBAC context.

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 on when to use this tool vs alternatives like itglue_get_group or itglue_search_organizations. Lacks context for selecting among list/search tools.

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