k8s_get_clusterrolebindings

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states that the tool lists bindings, without mentioning authentication needs, response format, pagination, or any side effects. This is minimal disclosure.

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 a single sentence of 10 words, directly stating the tool's purpose without any unnecessary words. It is appropriately sized and 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?

Despite low complexity (1 parameter, no output schema), the description is incomplete. It does not describe how to use the context parameter, what the output looks like, or any filtering/pagination behavior. Essential details for effective tool invocation are missing.

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 schema has 0% description coverage; the sole required parameter 'context' (string) is not explained. The description does not add any meaning beyond the schema, failing to clarify what values are valid or how to obtain them. This leaves the agent uninformed.

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 states 'List RBAC ClusterRoleBindings showing cluster-wide role assignments.' It clearly specifies the action (List), resource (RBAC ClusterRoleBindings), and scope (cluster-wide), distinguishing it from sibling tools like k8s_get_rolebindings (namespace-scoped) and k8s_get_clusterroles (roles themselves).

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 role assignments but provides no explicit guidance on when to use this tool versus alternatives like k8s_get_rolebindings or k8s_get_clusterroles. No when-not-to-use or prerequisite information is given.

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