pbs_realm_ldap_list

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

With no annotations, the description provides the key behavioral trait 'READ-ONLY', which is a strong safety signal. It also notes a configuration requirement. However, it does not elaborate on other behavioral aspects like idempotency or error conditions, but the output schema fills in return structure.

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 sentences, very concise, with the key information front-loaded (READ-ONLY label). No extraneous 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?

Given the simplicity of the tool (one optional parameter, output schema present), the description is complete. It distinguishes from the sibling get tool and mentions the config requirement, which suffices for correct invocation.

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%, so the baseline is 3. The description does not mention the single parameter 'proximo_target', but the schema provides a complete description of it. Hence, no additional value from 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 clearly states it lists configured LDAP realms, with the verb 'list' and resource 'LDAP realms'. It distinguishes itself from the sibling tool pbs_realm_ldap_get, which is used for a single realm's full config.

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?

Explicitly says to use pbs_realm_ldap_get for one realm's full config, indicating when not to use this tool. Also mentions the prerequisite 'Needs PROXIMO_PBS_* config', guiding the user on setup.

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