azure_get_aks_credentials

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

With no annotations, the description carries full burden. It discloses that the tool extracts credentials and returns cluster details, and mentions admin credentials are only available with proper permissions. However, it does not mention any destructive side effects, rate limits, or prerequisites beyond what the schema implies.

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?

The description is two tight sentences plus a one-line use-case note. It front-loads the main action and all content is relevant. No wasted words.

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 5 parameters and no output schema, the description lists return values but does not explain the format or structure of the kubeconfig. For a tool that returns complex data, more detail on how credentials are returned (e.g., as text, file, or structured data) would improve completeness.

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%, so baseline is 3. The description does not add extra meaning to parameters; it only mentions adminAccess implicitly via the 'admin credentials (if available)' note. No additional guidance beyond schema is provided.

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 clearly states the tool extracts AKS cluster credentials and kubeconfig for kubectl access. It lists return values and distinguishes itself from sibling tools like azure_scan_aks_full or azure_analyze_rbac_privesc.

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 includes an 'OFFENSIVE USE' section indicating when to use for exploitation, but it does not explicitly state when not to use the tool or compare it to alternatives like azure_get_resource_details. No exclusion criteria are provided.

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