generate_spiral_mission

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

No annotations provided, so description must disclose behavioral traits. It states mission auto-saves and returns ID and waypoint count, which is valuable. However, it does not disclose whether the operation is destructive (overwrites existing missions) or requires authentication/permissions. With zero annotations, the description could be more complete, but the auto-save disclosure is a plus.

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: first explains purpose and use case, second notes auto-save behavior. No filler, but could be slightly more compact by merging phrases.

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 12 parameters (6 required) and no output schema, the description explains the output (saved mission with ID, waypoint count) and implies input constraints via schema. For a complex mission generation tool, it is moderately complete; missing details on limits like waypoint max or GPS coordinate format are minor.

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 92% (11 of 12 params have descriptions). The description adds no further parameter explanations beyond the schema. Baseline 3 is appropriate.

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 describes a specific verb ('Generate') and resource ('spiral survey mission') with behavior (expanding/contracting from center). Distinguishes from siblings like 'generate_grid_survey' or 'generate_orbit_mission' by mentioning spiral pattern, search patterns, and radial coverage.

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?

States use cases ('search patterns or radial coverage') but does not explicitly say when not to use or compare to alternative tools. Context is clear enough for typical agent decision.

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