tigergraph__drop_loading_job

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

The annotations already provide destructiveHint=true, so the description adds little beyond restating that this deletes a loading job. It does not disclose irreversibility, effects on active loading processes, or behavior if the job does not exist. No extra behavioral context is provided beyond what annotations already convey.

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?

A single, front-loaded sentence with no filler. Every word contributes to the meaning, and the parenthetical '(delete)' usefully clarifies the technical term 'drop'.

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?

For a simple destructive tool with full schema coverage and clear annotations, the description is nearly complete for selecting and invoking the tool. It could mention that the action is permanent or advise listing loading jobs first, but the combination of schema and annotations covers the essential call requirements.

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%, and the schema already documents job_name, profile, and graph_name clearly. The description adds no parameter-level details, but with full schema coverage this is acceptable.

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 a specific verb ('Drop (delete)') and resource ('a loading job'), so an agent can tell this is the deletion tool for loading jobs. It does not explicitly contrast with related drop tools (drop_graph, drop_query, drop_data_source), but the resource noun is specific enough to avoid confusion.

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?

No guidance is given about when to use this tool versus alternatives such as get_loading_jobs or create_loading_job. There is no warning to list/verify jobs before deleting, and no mention of whether dropping affects running jobs. Usage context is only implied by the destructive name.

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