createAtcRun

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states 'Creates an ATC run' without explaining what creation entails, such as whether it's idempotent, requires specific permissions, triggers background processes, or returns a run ID. This is inadequate for a mutation tool with zero annotation coverage.

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 extremely concise with a single sentence, 'Creates an ATC run.' It is front-loaded and wastes no words, though this brevity contributes to its lack of helpfulness.

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 complexity of a creation tool with no annotations and no output schema, the description is completely inadequate. It fails to explain what an ATC run is, what the tool does beyond the name, behavioral traits, or expected outcomes, leaving significant gaps for an AI agent.

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%, so the schema already documents all parameters (variant, mainUrl, maxResults). The description adds no additional meaning beyond what the schema provides, such as explaining how these parameters interact or their impact on the ATC run. The baseline score of 3 reflects adequate coverage from the schema alone.

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 'Creates an ATC run' is a tautology that merely restates the tool name without specifying what an ATC run is or what resources it involves. It lacks a clear verb+resource combination and doesn't differentiate from sibling tools like 'atcCheckVariant' or 'atcCustomizing'.

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 provided on when to use this tool versus alternatives. There's no mention of prerequisites, context, or exclusions, leaving the agent with no information about appropriate usage scenarios.

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