Argocd Can I

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, openWorldHint), so the bar is lower, yet the description still adds real value: it discloses the return shape {allowed: bool, ...} and the non-obvious detail that the underlying API answers with the string yes/no rather than a boolean. It also implicitly signals the check is scoped to 'the current account' (caller credentials), which the schema does not convey.

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, zero filler, front-loaded with the core operation and followed immediately by the return-value caveat. Every clause earns its place.

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?

An output schema exists so return values need no elaboration, and parameters are fully documented in the schema. The only missing piece is guidance on when to invoke the check and how to interpret a denial; for a simple read-only probe this is close to 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 100% with enums documented for action and resource, so the schema carries the parameter burden. The description only restates the resource/action/subresource composition without adding format or semantic detail beyond the schema; 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 and resource: 'Check whether the current account may perform resource/action on a subresource.' It is unambiguously an RBAC permission probe, which no sibling tool performs (siblings are all get/list/create/patch/delete operations). It does not explicitly contrast itself with siblings, but the purpose is clear enough that no confusion arises.

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?

Usage is only implied: an agent can infer this is a pre-flight permission check before attempting an operation, but the description never states when to call it, when not to, or what to do with the result. There is no explicit alternative or condition given.

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