list_app_projects

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

No annotations are provided, so the description carries the full burden. It does convey a read-only listing behavior and the nature of the returned data, but it adds no context about scope, authentication needs, pagination, or how the cluster/namespace parameters affect the operation. For a low-risk read tool this is adequate but thin.

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?

A single sentence that front-loads the verb and resource and packs the key return fields compactly. Every word earns its place with no filler or repetition.

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, has zero required parameters, and an output schema exists, so return-value documentation is not the description's job. However, parameter semantics and usage routing among the many GitOps siblings remain unexplained, leaving an agent to guess. Adequate for a trivial list call, but not complete.

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 description coverage is 0% and the description never mentions the cluster or namespace parameters, so it does not compensate for the schema gap. The parameter names and the 'openshift-gitops' default hint at their purpose, but the description adds no meaning beyond what the schema fields literally show.

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 ('List') and names the exact resource ('ArgoCD AppProjects') plus the returned data categories (source repos, destinations, cluster resource access). The resource name distinguishes it from sibling tools like list_gitops_applications and list_gitops_clusters, so an agent can disambiguate without opening schemas.

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 on when to use this tool versus the many ArgoCD/GitOps siblings (list_gitops_applications, list_gitops_clusters) or generic alternatives like run_oc_command. No conditions, exclusions, or prerequisites are stated, leaving the agent to infer usage solely from the tool name.

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