create_mission

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

No annotations are present, and the description only states that it creates a mission. It does not disclose side effects, required permissions, or any constraints on the mission object. The nondescript 'Mission details' parameter adds no behavioral insight.

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 very concise (one short sentence), but it sacrifices helpfulness. It could include more context without being verbose, such as typical usage or a link to mission structure.

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 lack of annotations and output schema, the description is incomplete. It does not explain what a mission is, what happens upon creation, or how to interpret the response. The nested object parameter further demands more detail.

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 100%, and the description adds no extra meaning beyond what the schema provides. The nested 'mission' object is opaque, but the schema already describes both parameters minimally.

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 'Create a new mission' clearly states the action and resource, but it does not distinguish this tool from siblings like 'create_project_plan' or 'create_ticket', leaving ambiguity about what a mission specifically is.

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_project_plan, create_ticket). The description offers no context about prerequisites or scenarios for creation.

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