generate_spiral_mission

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

With no annotations, the description discloses that the tool automatically saves the mission to the account and returns the saved mission with ID and waypoint count. However, it does not elaborate on potential side effects, permissions, or error conditions.

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 sentences with no waste. The first sentence states the core action and direction, the second adds automation and return value info. It is front-loaded and efficient.

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 high schema coverage and the description explaining the output (saved mission with ID and waypoint count), the tool is adequately documented. However, some edge cases or parameter interactions are not addressed.

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 high at 92%, so the baseline is 3. The description does not add meaningful parameter-specific context beyond what the schema already provides (e.g., no explanation of start_radius vs end_radius relationships).

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 it generates a spiral survey mission expanding outward or contracting inward, for search patterns or radial coverage. It distinguishes from sibling tools like generate_grid_survey and generate_orbit_mission by specifying the spiral pattern and purpose.

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?

The description provides context ('useful for search patterns or radial coverage') but does not explicitly state when to use this tool versus alternatives. It does not mention exclusions or when-not-to-use scenarios.

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