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

Annotations already declare readOnlyHint=true, so read safety is covered. The description adds real behavioral value by disclosing the returned shape (provider, full name, default branch) and the Bitbucket-specific workspace/repo_slug fields that later feed gitops_workspace and gitops_repo_slug, which is not derivable from any structured field.

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?

Three tight sentences, front-loaded with purpose before the workflow note and the return-field detail. Nothing is wasted, though the final clause about gitops_workspace/gitops_repo_slug is dense enough to slow a quick read.

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 output schema, the description carries the return-value burden and does so completely, naming the provider, full name, default branch, and Bitbucket extras, plus the sequencing precondition. An agent has everything needed to call and interpret this tool.

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?

Only one parameter and schema coverage is 100%; the schema already documents credential_id as the UUID from list_gitops_credentials. The description restates the provider constraint (GitHub or Bitbucket Cloud) but adds no format or syntax detail beyond the schema, so the baseline 3 applies.

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) and resource (repositories reachable by a GitHub or Bitbucket Cloud credential for GitOps), scoping it tightly enough to separate it from the generic github_list_repositories and from list_gitops_credentials. The provider constraint is stated up front.

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?

Gives an explicit workflow precondition: 'Use after list_gitops_credentials to let the user pick a repository for GitOps setup at cluster creation.' That is clear when-to-use guidance, but it never names a competing alternative or states when not to use it, so it falls short of a full 5.

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