list_clients

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

No annotations are provided, so the description carries the burden. It clearly signals a read-only operation via '[READ]' and discloses important behaviors: normalization of fields, truncation flag semantics, and null field handling. It does not mention permissions or rate limits, but for a list operation with return-format detail, this is strong coverage.

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 compact and front-loaded with the [READ] tag and clear purpose. The Args and Returns sections are concise, and every sentence adds value—especially the clarification about truncated measurement and null pkceMethod. No wasted words.

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 tool's simplicity, no output schema, and no annotations, the description provides complete context: purpose, parameter semantics, return structure, and edge-case behavior (truncated flag, null fields). It is self-contained for an agent to invoke correctly. Additional details like error handling are unnecessary for this level.

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 input schema has no descriptions (0% coverage), so the description fully compensates. It explains max_results as 'Page bound (default 200)' and target as 'IdP target name from config; omit for the default', adding meaning beyond the bare parameter names. There is no ambiguity about how to use them.

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 a specific action ('list') and resource ('OAuth/OIDC clients in the realm'), with normalization details. This distinguishes it from sibling tools like client_detail (which focuses on a single client) and other list tools (e.g., list_users, list_identity_providers).

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?

Usage is implied by the verb 'list' and the parameters, but there are no explicit when-to-use or when-not-to-use instructions, and no mention of alternative tools. For instance, it does not clarify when to use this instead of client_detail or client_sessions. The target parameter guidance is present but limited to configuration context.

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