etl_star_historical

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

With no annotations, the description carries the full behavioral burden. It does disclose the key destructive trait 'overwrite', which is essential safety information for an agent. However, it omits consequences such as whether tables are dropped/recreated, whether the operation is transactional, and what happens to existing dependent objects.

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 efficient sentence with no filler and the core action front-loaded. It is concise, though the brevity leaves out details that are penalized in other dimensions.

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 destructive ETL tool with no annotations and no output schema, the description is too thin. It leaves the as_job parameter unexplained and does not state expected completion signals, side effects, or the relationship to etl_star_cdc, making confident invocation harder than necessary.

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 schema has one boolean parameter 'as_job' with 0% description coverage, and the description does not explain what it controls. The agent cannot know whether setting as_job to false changes execution mode, output, or behavior, so the description fails to compensate for the schema's silence.

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 ('Rebuild') with a clear resource ('star-schema dims and fact_sales') and source ('from OLTP'), and flags 'overwrite' to signal a full replacement. It does not explicitly differentiate from sibling etl_star_cdc, though the word 'historical' and the rebuild/overwrite language weakly distinguish it as a full load.

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 explicit guidance is given about when to use this tool instead of etl_star_cdc, generate_historical_oltp, or other siblings. An agent must infer from the name and the words 'Rebuild'/'overwrite' that this is a full refresh, but there is no direct statement of intended use or exclusions.

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