Get

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered structurally. The description adds nothing beyond the title – no statement of what is returned, what ID is needed, or what happens with an empty params_json.

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 short sentences with no padding, but the first is a pure name restatement and the second is boilerplate ("Manage ... operations") that earns no place. Efficient in size, empty in content.

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 read tool whose only input is a generic JSON bucket, the description should say what to put in it; instead it says nothing. No output schema exists, so the description also carries the burden of describing the return value, which it does not.

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%, so the baseline would be 3, but the single parameter is an opaque "JSON string of parameters" blob and the description supplies no key names or shape for a deploy-token get. With one parameter and full schema text, the description should at least hint at the expected keys, and it does not.

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 restates the name ("Get (gitlab_deploy_tokens)") and offers only the generic "Manage gitlab deploy tokens operations." It does not distinguish this tool from the many sibling getters (gitlab_get_deploy_tokens, gitlab_get_project_deploy_token, gitlab_get_group_deploy_tokens, gitlab_get_project_deploy_tokens), nor does it say which deploy-token scope is retrieved.

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?

"Manage ... operations" gives no when-to-use, no prerequisites, and no routing to alternatives, even though several near-identical siblings exist. An agent has nothing to select on besides guessing from the name.

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