create_mission

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

The description only reiterates the creation action, adding no behavioral insight beyond the annotation `destructiveHint: false`. It omits disclosures about side effects, required permissions, or post-creation behavior.

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 concise, using one introductory sentence followed by a clear bullet list of arguments. Every word serves a purpose, though the list format is slightly redundant with the schema.

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 5 parameters and an output schema, the description fails to explain the return value, prerequisites (e.g., agent existence), or how to handle optional parameters. It does not leverage sibling tool context to guide usage.

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?

The description adds brief explanations for all five parameters, covering the 0% schema coverage. However, the explanations are minimal (e.g., 'Constraints on execution') and lack specificity about format or constraints.

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 verb 'Create' and the resource 'mission (bounded job)', making the tool's purpose unambiguous. It effectively distinguishes from sibling tools like cancel_mission and update_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?

No guidance is provided on when to use this tool versus alternatives (e.g., create vs update). The description lacks any context about prerequisites or scenarios where this tool is appropriate.

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