k8s_get_clusterroles

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

No annotations are provided, so the description carries full burden. It only states it lists roles and permission rules, but omits details about authorization needed, output format, or that it is a read-only operation. Minimal behavioral context beyond purpose.

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 with no wasted words. The first sentence states the primary action, and the second adds relevant scope information. Properly front-loaded.

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?

Given 1 parameter with no description, no output schema, and related sibling tools, the description is too sparse. It doesn't explain what 'permission rules' entail or how to interpret the output, leaving the agent under-informed.

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?

The single parameter 'context' has no schema description (0% coverage) and the tool description does not mention it at all. The agent receives no guidance on what 'context' represents or how to use it.

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 verb 'List' and the resource 'RBAC ClusterRoles', and the second sentence distinguishes them from namespaced roles by noting their cluster-wide scope. This differentiates it from sibling tools like k8s_get_roles and k8s_get_clusterrolebindings.

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 implies usage for listing cluster-wide RBAC roles by mentioning cluster-wide permissions vs per-namespace binding, but it does not explicitly name alternatives or state when not to use the tool compared to siblings.

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