Download any instance URL

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds valuable context: it specifies the authenticated GET nature, and highlights response formatting ('Returns images as images and text as text'), which is not derivable from annotations alone.

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 sentences, front-loaded with the core purpose. Every word adds value: the verb, resource scope, examples, and return-behavior note. No redundancy or filler.

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?

The tool is simple (2 params, no output schema), and the description covers purpose, examples, and response types. It does not explicitly note limitations (e.g., unsupported content types) but overall is sufficiently complete for an agent to select and invoke it correctly.

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 clear parameter descriptions, so baseline is 3. The tool description adds value by giving concrete URL examples (job artifacts, raw files, avatars), helping agents understand what kinds of URLs are valid targets for the 'url' parameter.

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 uses a specific verb ('Authenticated GET') and identifies the resource ('arbitrary URL on the GitLab instance'), with concrete examples (job artifacts, raw files, avatars). It clearly distinguishes itself from sibling tools like gitlab_get_job_artifact or gitlab_get_file by being the generic URL-fetching tool.

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 usage as a catch-all for any instance URL by listing examples, but it does not explicitly state when to use this tool versus more specific siblings (e.g., gitlab_get_file, gitlab_get_job_artifact). No exclusions or alternative recommendations are given, leaving room for ambiguity.

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