pbs_realm_sync

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

No annotations exist, so description carries full burden. It states mutation, async return of UPID, and dry-run default, but does not explain what dry-run outputs or mention permissions/rate limits. The old param drop is helpful.

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 dense and front-loaded with key info, using a single paragraph with no fluff. Every sentence adds value.

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?

With an output schema presumably containing return details, the description covers mutation, async behavior, config, and key parameters. Dry-run behavior could be clearer, but overall adequate.

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 20% (only proximo_target has description). The description adds meaning for realm, confirm, dry_run (though slightly inconsistent with schema default), and remove_vanished, but does not cover all parameters completely.

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 'MUTATION: sync PBS auth realm (LDAP/AD) users,' using a specific verb and resource. It distinguishes itself from sibling tools, none of which are similar sync operations.

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 explains dry-run default, confirm execution, and remove_vanished behavior. It lacks explicit when-not-to-use or alternatives, but the usage context is clear.

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