ftrack_export_review_session_feedback_delayed_job

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

With no annotations available, the description carries full burden for behavioral disclosure. While 'delayed job' hints at asynchronous execution, it does not explain side effects, return behavior, job status monitoring, or permissions. The description is too sparse to inform the agent of what happens after export.

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, making it highly concise. However, it is perhaps too terse to be fully effective given the complexity of a delayed job, though this is more a completeness issue.

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 and no annotations, and the description does not explain the return value, job lifecycle, or how to check export results. With only a one-sentence description, the context is insufficient for an agent to fully understand the tool's behavior and outcome.

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 parameters ('options' and 'review_session_id') having descriptions. The tool description adds no additional parameter context, so the schema already carries the semantic weight; baseline 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 the tool's verb ('Export'), resource ('review session feedback'), and mode ('as a delayed job'), which distinguishes it from other delayed job tools like ftrack_csv_import_delayed_job. This unambiguously identifies the tool's primary function.

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, nor does it mention any prerequisites, exclusions, or specific scenarios. There is no explicit or implied usage context beyond the literal action.

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