ftrack_iconik_sync_structure_delayed_job

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

No annotations are present, so the description carries the full burden. It discloses only that it is a delayed job, but does not explain job lifecycle, how to monitor/retrieve results, side effects on existing structure, permissions, or whether it is destructive. This is insufficient for a syncing 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 short sentence with no redundancy. It is front-loaded with the core action. The brevity is not excessive but is more under-specification than elegant conciseness, so a 4 is appropriate.

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?

Given no output schema, no annotations, and a free-form options object, the description is incomplete. It does not mention what the tool returns (e.g., job ID, success status), how to retrieve job status, or what effects the sync has. This is a significant gap for a delayed job 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 description coverage is 100% with both project_id and options described, giving a baseline of 3. However, the options description ('Sync options') is vague and the tool description adds no further parameter meaning, so it does not elevate beyond baseline.

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 action (Sync), the resource (structure), the destination (iconik), and the mode (delayed job). It distinguishes from siblings like get_project_structure by specifying the external destination and asynchronous nature.

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?

No guidance is provided on when to use this tool over other delayed job tools or alternatives. It does not mention prerequisites, exclusions, or context such as 'use this when you want to push structure to iconik without waiting for completion.'

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