list_clients

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

No annotations exist, but the description transparently indicates a read-only listing operation. The behavior is straightforward and unlikely to have hidden side effects, though details like pagination are not mentioned (output schema may cover these).

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, concise sentence that conveys all necessary information without extraneous words. It is front-loaded and 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 zero-parameter input schema and the existence of an output schema, the description is complete for a simple list tool. It fully specifies what the tool returns without needing additional context.

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?

There are no parameters in the input schema, so schema description coverage is 100%. The description adds no parameter-level information beyond what the schema provides, which is appropriate for a parameterless tool.

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 SAML/OIDC clients in the realm' clearly identifies the verb (list) and resource (SAML/OIDC clients). It distinguishes from sibling tools that list users, events, or sessions.

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 (listing clients) but provides no explicit guidance on when to use this tool versus alternatives like get_client_sessions or search_users. No exclusions or prerequisites are mentioned.

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