tigergraph__run_loading_job_with_file

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

Annotations indicate readOnlyHint=false and destructiveHint=false, implying this is a mutating operation. The description only says the file is uploaded and loaded, but doesn't disclose side effects, error behavior, or that the loading job must be pre-defined. It doesn't add meaningful behavioral context beyond the annotations.

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 two sentences, efficient and to the point. It front-loads the action and resource. No wasted words, but it's arguably too terse for a tool of this complexity.

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 9 parameters and no output schema. The description doesn't explain return values, error handling, or how the loading job interacts with existing data. It doesn't mention that the job must already be created (via create_loading_job). For an agent, this is incomplete for safe invocation.

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 has 100% description coverage, so all parameters are documented in the schema. The tool description adds no additional parameter semantics; it doesn't elaborate on file_path, job_name, or any optional parameters beyond what the schema provides.

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 ('Execute a loading job') and the resource ('with a data file'), and mentions the upload. It doesn't explicitly name the sibling 'run_loading_job_with_data' to differentiate, but the phrase 'with a data file' implies the distinction. It's specific enough for an agent to understand the core purpose.

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 the sibling 'run_loading_job_with_data' or other loading job tools. It doesn't mention prerequisites like the loading job must already exist, or the file must be accessible. No exclusions or alternatives are given.

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