generate_orbit_mission

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

It discloses automatic saving and return of mission ID and waypoint count, important side effects. However, lacks details on error handling, permission requirements, or parameter validation beyond schema.

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 achieve high density: first sentence defines purpose, second adds behavioral details. No redundant content, front-loaded with key info.

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 9 parameters and no output schema, the description covers core functionality and return value. Missing explanations for drone_profile_id and error conditions, but overall adequate.

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 high (89%), so baseline is 3. The description adds no additional meaning beyond schema; drone_profile_id is undocumented in description.

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 generates an orbit/POI mission with waypoints facing center, distinguishing it from sibling tools like generate_grid_survey or generate_spiral_mission.

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 implies usage for circular orbits around a POI, but does not explicitly state when to use this versus alternatives or what prerequisites (e.g., drone profile) are needed.

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