pbs_realm_ldap_get

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

Read-only behavior is clearly stated. No annotation provided, so the description carries the burden. It does not mention specific permissions or rate limits, but for a simple read operation this is adequate.

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?

Extremely concise: two sentences, zero wasted words. The purpose is front-loaded and the prerequisite is clearly stated.

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, the description covers the essential purpose and prerequisite. An output schema exists for return values. Minor omission: no mention of what happens if realm does not exist.

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 schema already documents parameters. The description adds no additional meaning beyond the schema's field descriptions.

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?

Description clearly states 'get one LDAP realm's config' with a specific verb and resource. The READ-ONLY prefix distinguishes it from mutation siblings like create/update/delete.

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?

Explicit prerequisite 'Needs PROXIMO_PBS_* config' is helpful. However, it does not explicitly contrast with sibling tools like list or update, leaving the agent to infer when to use this vs alternatives.

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