keycloak_get_realm_flow_bindings

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

Annotations already declare readOnlyHint=true, and the description's 'Show' is consistent with a safe read operation. It adds useful context about which entry points are covered but does not disclose output shape or pagination; no annotation contradiction.

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?

Single sentence with no filler. The entry-point examples are high-value and make the behavior concrete without bloating the text.

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?

For a one-parameter read-only tool with a simple purpose and no output schema, the description gives enough to invoke it correctly. It doesn't explicitly describe the return structure, but the examples of entry points map the output domain adequately.

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 only parameter, realm, is fully documented in the schema with 100% coverage, including its default to KEYCLOAK_REALM. The description adds nothing about parameters, so it relies on the schema's sufficient description.

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 uses a specific verb 'Show', names the resource (flow bindings for realm authentication entry points), and gives concrete examples. This clearly separates it from sibling flow tools like list_authentication_flows.

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?

It clearly conveys that this tool is the source for authentication-flow-to-entry-point bindings, but it never explicitly states when to prefer it over siblings or offers exclusions. Usage context is implied rather than stated.

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