Get deploy tokens

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

The annotations already establish that this is a read-only, idempotent, non-destructive, open-world operation. The description adds a little useful context about the return wrapper and the ParameterError, but it does not disclose pagination behavior, filtering semantics, permission requirements, or how the many parameters affect the result.

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 short and front-loads the operation, but the Args/Returns/Raises boilerplate includes a non-informative '**kwargs' line. It is not verbose, but some of the text does not earn its place given the missing parameter and scoping details.

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 an 11-parameter list tool with 0% schema description coverage and no output schema, the description is substantially incomplete. It states the basic operation and return wrapper, but omits parameter meanings, scoping between global/project/group tokens, pagination, and other behavior needed to invoke it confidently.

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 schema has 11 parameters with 0% description coverage, and the description does not explain any of them. The only parameter-related text is a generic '**kwargs' note, which does not clarify name, token, scopes, page, per_page, max_pages, expires_at, username, group_id, or project_id.

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 clear verb and resource: 'Get all deploy tokens.' However, it does not distinguish this generic tool from siblings such as gitlab_get_project_deploy_tokens, gitlab_get_group_deploy_tokens, or gitlab_deploy_tokens_get, and the schema's project_id/group_id parameters imply scoped behavior that the description does not clarify.

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 gives no guidance about when to use this tool instead of the project-, group-, or token-specific deploy-token tools. It also does not explain whether 'all deploy tokens' means globally across projects/groups or can be narrowed by the documented project_id/group_id parameters.

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