ldap_modify

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

Without annotations, the description discloses the tool's blocking behavior (readOnly mode) and the three operations, adding transparency about its mutation scope and limitations.

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?

Two concise sentences: one describing the action, one a critical constraint. No extraneous information, efficient for an agent to parse.

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?

As a mutation tool without output schema or annotations, the description covers core functionality and a blocking condition but lacks details on return values, error handling, or prerequisites.

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 description coverage is 60%. The description adds context (single attribute modification) but does not compensate for missing descriptions for 'attribute' or 'operation' beyond what their names/enum imply.

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 the tool modifies an existing LDAP entry by adding, replacing, or deleting a single attribute's values, distinguishing it from siblings like ldap_add (new entries) and ldap_delete (entry deletion).

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 mentions a blocking condition (readOnly mode) but does not provide explicit guidance on when to use this tool vs. alternatives (e.g., ldap_add_bulk), leaving usage implicitly defined.

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