pbs_realm_ad_get

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

No annotations are provided, so the description carries full burden. It declares the operation as 'READ-ONLY', which is valuable, but does not disclose behavior on errors (e.g., if realm does not exist), authentication requirements beyond the config hint, or any side effects. Minimal behavioral context for an agent.

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, no redundancy—first sentence states purpose and read-only nature, second lists prerequisite. 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?

For a simple get operation with an output schema, the description covers core purpose and read-only hint. However, it lacks details on error scenarios or expected response behavior (though output schema exists). Adequate but could be more thorough.

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 description coverage is 100% (both parameters have descriptions). The description adds no new parameter details; it only restates the need for 'PROXIMO_PBS_* config', which is not parameter-specific. Baseline of 3 is appropriate as the schema already provides adequate semantic information.

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?

Clearly states 'get one AD realm's config' using specific verb 'get' and resource 'AD realm's config'. The 'READ-ONLY' prefix and contrast with sibling tools like pbs_realm_ad_create, pbs_realm_ad_delete, pbs_realm_ad_list, and pbs_realm_ad_update make it distinct.

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?

Implies usage for retrieving a single AD realm configuration, but does not explicitly state when to use this tool versus alternatives like pbs_realm_ad_list for multiple realms. The prerequisite 'Needs PROXIMO_PBS_* config' is mentioned, but no exclusion criteria or alternative suggestions are provided.

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