pbs_realm_pbs_get

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

No annotations provided, so description carries full burden. It states READ-ONLY behavior and a configuration prerequisite, which are useful for a simple get operation. Could add details about error handling or response scope, but 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?

The description is a single, well-structured sentence with a front-loaded READ-ONLY label. Every word serves a purpose, no fluff.

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 a simple get operation with output schema present, the description covers the key points: resource, read-only nature, and a prerequisite. It could optionally mention the return format, but output schema covers that.

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 single parameter 'proximo_target' is fully documented in the schema. The description does not add extra meaning beyond what is already in the schema, hence baseline score of 3.

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 'get the built-in PBS-auth realm's config', specifying a specific verb and resource. It distinguishes from siblings by noting 'built-in' realm, differentiating from other realm tools like pbs_realm_ad_get or pbs_realm_ldap_get.

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?

The description provides a prerequisite ('Needs PROXIMO_PBS_* config') and marks it as READ-ONLY, indicating when it's appropriate. It lacks explicit alternatives or when-not-to-use guidance, but the context from sibling names helps.

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