list_auth_flows

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

No behavioral traits beyond the basic 'list all' are disclosed. There is no mention of pagination, filtering, ordering, or the structure of the response. Since no annotations are provided, the description should compensate but fails to do so.

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 concise (one short sentence) but lacks structure and does not earn its place with additional valuable information. It is minimally adequate but not notably efficient.

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 the simplicity of the tool (single required parameter, no output schema), the description is adequate for a basic list operation. However, it is incomplete regarding potential pagination or error handling, though these may be implicitly understood.

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 coverage is 100% with the 'realm' parameter having a basic description 'Realm name'. The description does not add additional meaning or context beyond what the schema already provides, so baseline score of 3 is appropriate.

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 'List all authentication flows in the realm' uses a specific verb 'List' and clearly identifies the resource 'all authentication flows in the realm', distinguishing it from sibling tools like get_auth_flow (single) and create_auth_flow. It is precise and unambiguous.

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 provides no explicit guidance on when to use this tool versus alternatives, such as get_auth_flow for a single flow or create_auth_flow for creating one. No when-not-to-use or alternative mentions are present.

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