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

Annotations only declare readOnlyHint=true, and the description adds real domain behavior beyond that: the returned fields (id, name, provider, credential_scope, availability), the org-wins-over-personal precedence, and the meaning of shadowed_by_organisation_credential as a selection blocker. It stops short of auth/permission requirements, but for a parameterless read tool the disclosure is strong.

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?

Front-loaded with the core purpose, then supporting detail in descending order of importance (return fields, downstream naming, shadowing rule). It is one dense block rather than separated sentences, but every clause carries information an agent needs to use the list correctly.

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?

With no parameters, no output schema and only a readOnlyHint annotation, the description carries the full burden and does so: it covers what is listed, what comes back, why you would call it, and the one semantic trap (organisation shadowing) that would otherwise cause a bad selection.

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?

Zero input parameters, so there is nothing to disambiguate and the baseline is 4. The mention of gitops_credential_name and gitops_provider describes how a downstream create consumes the listed values rather than this tool's own inputs, which is helpful context but not parameter semantics.

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?

States a specific verb ('List') plus a tightly scoped resource ('git credentials available for GitOps integration: GitHub and Bitbucket Cloud, organisation and personal'). The scope qualifier cleanly separates it from the generic list_credentials / list_provider_credentials / list_helm_registry_credentials siblings without needing to name them.

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?

It gives explicit context for the listing: 'Used during cluster creation to optionally connect a GitOps repository for GitOps-driven deployment of cloud components (hcloud CCM, CSI)', and the shadowing rule tells the agent which credentials must not be selected by name. It never names an alternative tool (e.g. list_credentials for non-GitOps credentials), so the exclusion side is implied rather than stated.

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