pbs_realm_ad_list

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

Declares READ-ONLY, indicating safe operation without side effects. Mentions config dependency. No annotations exist, so description carries full burden but could elaborate on behavior if config is missing or what happens on success/failure.

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 with two sentences. Front-loaded with 'READ-ONLY: list configured AD realms.' No superfluous 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 output schema exists, description sufficiently covers purpose, usage, and behavioral context. Minor gap: does not specify that it lists all realms, but that is implied. Adequate for a list tool.

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%; the single parameter is fully described in the schema. Description adds no extra meaning beyond the schema for the parameter.

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 'list configured AD realms' with a specific verb and resource. It distinguishes from sibling pbs_realm_ad_get by noting that tool retrieves one 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 marks as READ-ONLY and suggests using pbs_realm_ad_get for detailed config. Mentions prerequisite 'Needs PROXIMO_PBS_* config.' Sibling differentiation is provided, though could be more explicit about when not to use.

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