update_mission

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

The description discloses the merge behavior: 'omitted fields remain unchanged'. Without annotations, this is essential behavioral context. It implies an update operation, which is consistent with the name.

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, front-loaded with purpose, then usage hint. No wasted words. Could perhaps add a bit more detail on parameters without being verbose.

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 no output schema and moderate complexity (6 params), the description lacks details on return values, possible errors, or permissions. It is adequate but not fully complete.

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 33%, but the description adds general behavioral info rather than explaining specific parameters. The description does not compensate for the low coverage, but the schema does provide some descriptions for mission_id and waypoints.

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 updates an existing mission, with specific verb 'Update' and resource 'mission'. It distinguishes from sibling 'create_mission' and 'duplicate_mission' by mentioning 'Fetches the current version and merges your changes'.

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?

Description indicates to use list_missions to find mission IDs, guiding when to use this tool. However, it does not explicitly state when not to use it or provide alternatives for other operations.

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