ldap_add_bulk

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

With no annotations provided, the description fully discloses key behaviors: sequential addition, per-entry success/failure reporting, non-blocking on errors, and being blocked by readOnly mode. This exceeds the minimum needed and gives the agent a clear understanding of the tool's behavior.

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 extremely concise with only three sentences that are front-loaded with the core purpose and key behavioral details. Every sentence adds necessary information, and there is no redundancy or 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?

The description covers the tool's behavior and constraints well, but it does not explain the return format or structure of the per-entry success/failure report. Given that there is no output schema, a brief note on what the response looks like would improve completeness. However, it still provides enough for an agent to understand how to use the tool.

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% with detailed descriptions for both parameters, including an example for 'entries'. The description text does not add additional parameter semantics beyond what is in the schema, but this is acceptable given the high schema coverage. Thus, a baseline score of 3 is appropriate.

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 that the tool creates multiple LDAP entries in one call, specifically for seeding test/sample data. It uses a specific verb ('Create') and resource ('multiple LDAP entries'), and the mention of 'bulk' in the name and 'one call' distinguishes it from single-entry tools like ldap_add.

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 that there is no native multi-entry add in LDAP, so this tool is necessary for bulk operations. It also clarifies that entries are added sequentially with per-entry reporting, not aborting on first error, which helps the agent decide when to use this versus looping ldap_add. Additionally, it notes the constraint that it's blocked when readOnly mode is enabled.

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