preprocess_with_gui

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

With no annotations, the description carries the full burden. It mentions prerequisites and headless mode but does not disclose potential side effects, failures, or what the GUI launch entails (e.g., blocking, interactive behavior, error handling). Significant behavioral gaps remain.

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 short, front-loaded sentences with no redundant information. The parenthetical prerequisite is appropriately placed. Every word 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?

The tool description is minimal and does not explain how it fits into the preprocessing pipeline, what the GUI performs, or what the user should expect. Although an output schema exists, the description lacks sufficient behavioral and integration context to be fully self-contained.

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 0% and the description does not mention the 'project_dir' parameter at all. The parameter name gives a hint, but the description fails to explain its role in launching the GUI. No compensation for the lack of schema descriptions.

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 tool's action ('Launches') and target resource ('full Naztronomy-Smart_Telescope_PP.py GUI') with a specific mode ('headless'). This distinguishes it from sibling tools like process_seestar_mosaic or check_siril_version.

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?

Usage is implied: this tool is for launching the GUI headlessly. It lists a prerequisite but provides no explicit when/when-not guidance or comparison to alternative tools. The prerequisite gives some context but lacks exclusions.

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