k8s_get_rolebindings

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

With no annotations, the description carries full burden. It indicates a read-only listing operation, and the 'Omit namespace for all namespaces' note provides behavioral insight. However, it lacks details on authentication, rate limits, or result format.

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 concise sentences front-load the purpose and include a key usage tip. No wasted words; every sentence 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?

Given no output schema and no annotations, the description covers the core listing functionality and namespace behavior but neglects to explain the 'context' parameter or return values. Adequate but with a clear gap.

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%, so the description must compensate. It explains the namespace parameter's effect ('Omit namespace for all namespaces') but does not describe the required 'context' parameter. This is partial but meaningful beyond the schema.

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 'List RBAC RoleBindings showing which subjects are bound to which roles.' It uses a specific verb ('List') and resource, and distinguishes from siblings like k8s_get_roles and k8s_get_clusterrolebindings by mentioning namespace scope and the 'Omit namespace for all namespaces' note.

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?

No explicit guidance on when to use this tool vs. siblings like k8s_get_clusterrolebindings or k8s_get_roles. The description only implies namespace-scoped operation but does not state prerequisites or alternatives.

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