ftrack_create

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

No annotations are provided, so the description must disclose behavioral traits. It does not mention side effects, required permissions, whether changes are reversible, or any return value. The phrase 'Create a new entity' is essentially a restatement of the tool name and offers no additional behavioral context.

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 concise sentence with no wasted words. It is front-loaded and efficient, though it is perhaps too brief to be maximally useful. It does not suffer from verbosity, so it scores reasonably well on conciseness.

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 2 parameters, no output schema, and no annotations, the description is severely incomplete. It does not explain what the tool returns, how to structure entity_data, or any side effects. A create operation typically needs to convey success/failure and resulting object information, which is entirely absent.

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?

The input schema fully describes both parameters (entity_type and entity_data) with 100% coverage. The description adds no extra meaning beyond the schema, aligning with the baseline of 3 for high schema coverage. It does not compensate for any hidden constraints or provide examples of valid entity_data structures.

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 action ('Create a new entity') and identifies the resource ('in ftrack'). It is clear but does not differentiate from similar siblings like ftrack_create_note, which also creates an entity. The schema provides examples of entity types, so the purpose is understandable but lacks explicit scope.

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 guidance on when to use this tool versus alternatives such as ftrack_update or ftrack_delete, nor any exclusions or prerequisites. The description simply states the action without contextual direction, leaving the agent to infer usage.

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