sac_create_import_job

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

No annotations provided, so description carries full burden. States it allocates a staging area and returns a jobId, which is helpful. However, it does not disclose potential side effects (e.g., cost, limits), authorization requirements, or the exact nature of the staging area. The behavioral impact is partially transparent but could be improved.

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?

Two sentences, each providing essential information. Front-loaded with the primary purpose. No redundant or filler content. Every sentence earns its place.

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 the tool has 3 parameters and no output schema, the description covers the key aspects: creation of a job, allocation of staging area, parameter choices, and output (jobId). However, it could include more details about the staging area's capacity or cleanup to be fully complete for an agent unfamiliar with the system.

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 coverage is 100% with descriptions for all three parameters. The description adds significant value by explaining the default value for dataType and the condition for dimensionName (required when dataType='masterData'), which goes beyond the schema and clarifies usage.

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?

Clearly states the tool creates a new data import job for a model and allocates a staging area. The verb 'create' and resource 'import job' are specific. Distinguishes from siblings like sac_post_import_data, sac_validate_import, sac_run_import by being the initial step.

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?

Provides explicit guidance on specifying dataType (factData or masterData) and mentions that dimensionName is required for masterData. Implicitly indicates this is the first step in a multi-step import process by noting it returns a jobId for subsequent operations, but does not explicitly state when not to use or list prerequisites like model existence.

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