ftrack_delete_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 explaining behavior. It says 'Create a delete delayed job' but does not disclose whether the deletion is asynchronous, what the return value is, or any side effects (e.g., irreversibility). The term 'delayed' is the only hint, but it is insufficient.

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 that states the core purpose without unnecessary words. It is front-loaded with the action verb 'Create' and the resource. The wording could be smoother, but it is concise and to the point.

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?

This is a simple tool with no annotations and no output schema, yet the description lacks essential context. It does not explain what a 'delayed job' is, how to track it, or mention the alternative immediate deletion via ftrack_delete. An agent would have difficulty understanding the tool's role in a workflow without additional context.

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 (entity_id and entity_type) clearly described. The description adds no new meaning beyond the schema, so a baseline score of 3 is appropriate. It does not explain how these parameters relate to 'batch entity deletion' beyond what the schema says.

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 specific verb 'Create' and identifies the resource as 'delete delayed job' for 'batch entity deletion.' This distinguishes it from the sibling ftrack_delete tool, which likely performs immediate deletion. However, the phrasing 'delete delayed job' is slightly ambiguous (could be misread as deleting a job), though the purpose clarifies it.

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?

There is no explicit guidance on when to use this tool versus ftrack_delete or other deletion methods. It implies use for batch deletion, but does not state prerequisites, exclusions, or scenarios where immediate deletion is preferred. The agent is left to infer usage from the name and brief description.

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