manage_launch

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

Describes destructive behavior in detail: 'delete removes the launch and all its sections and tasks.' Adds context beyond destructiveHint annotation by specifying what is removed. Also lists failure conditions.

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?

Concise with bullet-like structure. Could be slightly more structured (e.g., separate sections), but no wasted words. Efficiently conveys key information.

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?

Covers all aspects: actions, required parameters per action, return values, failure conditions, and destructive warning. No output schema but returns are described. Sufficient for agent to use correctly.

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%, baseline 3. The description adds meaningful mapping of parameters to actions (e.g., create requires name and date, update/delete require launch_id). Better than just repeating schema.

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 three actions (create, update, delete) and the resource (launch). It distinguishes from siblings like get_launch (read-only) and other manage_ tools (different resources).

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?

Provides explicit USE WHEN triggers for each action and FAILS WHEN conditions. However, does not explicitly mention when to choose alternatives like get_launch for reading.

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