List CI/CD Catalog Resources

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

Annotations already indicate readOnlyHint=true, so the description adds marginal value. It mentions 'cursor pagination', which provides some behavioral context beyond the annotations, but lacks details about pagination behavior or return format.

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 sentence, concise but too vague. It front-loads the main action but omits essential detail, sacrificing completeness for brevity.

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 8 parameters with 0% schema coverage and no output schema, the description is severely incomplete. It fails to explain pagination parameters, filtering options, or return value, leaving the agent without critical invocation details.

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%. The description does not explain any of the 8 parameters (sort, after, first, scope, search, topics, group_ids, verification_level) beyond generic 'catalog filters'. No semantics added.

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 verb ('List'), resource ('GitLab CI/CD Catalog resources'), and mentions pagination and filters. However, it lacks specificity about what constitutes a 'catalog resource' and does not distinguish the tool from its sibling 'gitlab_get_ci_catalog_resource'.

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 such as 'gitlab_get_ci_catalog_resource' or other list tools. The description does not specify context or exclusions.

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