ftrack_sync_ldap_users_delayed_job

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'Sync LDAP users as a delayed job' without explaining what syncing entails (creation/update/deactivation), side effects, permission requirements, asynchronous execution details, or error behavior. This is a serious gap for a mutation-like operation.

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 a single, front-loaded sentence with no wasted words. It is concise and easy to scan, but it lacks additional structuring such as prerequisites or parameter hints. Given its brevity, it earns a high score for conciseness, though other dimensions suffer from under-specification.

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 tool has an opaque 'options' object parameter, no output schema, and no annotations. The description is far too minimal to be complete: it does not explain what options are valid, what happens after scheduling a delayed job, how to monitor it, or what the agent should expect. There is no context for correct invocation.

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% because the single parameter 'options' has a description ('LDAP sync options'), so baseline 3 applies. However, the description adds no extra meaning beyond the schema; 'LDAP sync options' is minimal and the object allows arbitrary additional properties, so the agent has no concrete keys or value formats. The description does not compensate.

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 a clear verb ('Sync') and resource ('LDAP users') with mode ('as a delayed job'). It distinguishes from sibling delayed job tools by naming LDAP users specifically, though 'sync' is somewhat generic and could fail to indicate push/pull direction or update semantics.

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 provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, typical scenarios, or mention any sibling tools (e.g., ftrack_csv_import_delayed_job) or exclusions, leaving the agent without usage direction.

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