ldap_operations

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and non-idempotent, so the safety profile is covered. The description adds value by attributing destructiveness to the sync action specifically and warning that it materially changes users, but it does not mention permission requirements, rate limits, or scope of the sync.

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?

Three sentences, front-loaded with the two capabilities, followed by the critical safety constraint. No filler and every sentence carries distinct information.

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?

An output schema exists, so return values need no prose. For a single-parameter tool with destructive capability, the description covers capability, value semantics, and the guardrail against unintended sync — nothing an agent needs to call it safely is missing.

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 0% (a bare required string with no enum), so the description carries the full burden and does so: it enumerates the accepted values (test, sync) and explains the semantics and consequence of each. There is no ambiguity about what values are legal.

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 states two concrete operations on a specific resource: testing the Snipe-IT LDAP connection and synchronizing LDAP users. It names the two action values and their distinct effects, so an agent can tell this apart from generic user-write siblings without opening the schema.

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?

It gives explicit when-to-use guidance per action (test = connectivity check only; sync = only when synchronization was explicitly requested) and an explicit prohibition (never infer sync from a test request). The routing logic between the two modes is fully spelled out.

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