ftrack_csv_import_delayed_job

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

With no annotations, the description must disclose behavioral traits. It simply says 'Create a CSV import delayed job' without mentioning that this is an asynchronous operation, what side effects occur, whether it mutates data, or what happens to the job after creation. No behavioral disclosure is present.

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 sentence and is very concise with no fluff. However, it is so terse that it sacrifices useful information; it reads more like a label than a meaningful explanation. This is acceptable but not exemplary.

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 no output schema, no annotations, and a free-form object parameter. The description does not explain what a delayed job is, what data job_data should contain, or what the response will look like. This is completely inadequate for an agent to use the tool effectively.

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% for the single parameter, and the parameter has a description ('CSV import job data'), so the baseline is 3. The tool description does not add any details about the expected structure of job_data beyond the schema, so it neither enhances nor detracts from the schema.

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 uses a clear verb ('Create') and resource ('CSV import delayed job'), and the 'CSV import' qualifier distinguishes it from sibling delayed-job tools like ftrack_export_review_session_feedback_delayed_job. However, it lacks any additional scope or details beyond what the name already implies, so it is clear but minimal.

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, when not to use it, or which alternatives (e.g., ftrack_create or other delayed-job tools) might be more appropriate. It only states the action without any context or exclusions.

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