pbs_realm_ad_delete

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

No annotations provided, so description carries full burden. It discloses mutation nature, permanent deletion, dry-run default, effect on user login, synchronous execution, return type (dict), no UPID, and config requirement. Highly transparent.

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 (three sentences) yet packed with critical information: mutation level, dry-run behavior, effect, execution toggle, sync nature, and config requirement. Every sentence earns its place.

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?

Covers most essential aspects for a deletion tool with 4 parameters and an output schema. Explains dry-run mechanism and consequences. Lacks detail on return dict format, but output schema likely covers that. Good overall.

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 baseline 3. Description adds context for confirm (dry-run vs execute) and mentions realm, but does not detail digest or proximo_target beyond schema. Adequate but not exceptional.

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 it permanently deletes an AD realm. Distinguishes from sibling tools like pbs_realm_ad_create, pbs_realm_ad_get, and pbs_realm_ad_update by specifying the delete action.

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?

Provides clear context: dry-run by default, confirm=True executes. Mentions dependency on PROXIMO_PBS_* config. However, no explicit when-not-to-use or alternative tools guidance, though the sibling set makes it obvious.

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