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

Beyond the sparse annotation (readOnlyHint: false), the description discloses that deployment consumes bandwidth, that all:true skips drones exceeding remaining bandwidth, and that the drone must be in the bay. This gives the agent meaningful behavioral expectations without contradicting the annotation.

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 packs prerequisites, bandwidth cost, related tools, and the all parameter behavior into one dense but efficient sentence. It is front-loaded with the core purpose and avoids filler, though the parenthetical chain could be restructured for easier scanning.

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?

For a simple deploy action, the description covers the main operational facts: prerequisite state, resource cost, all-mode behavior, and related tools. It does not describe the response or error cases, but this is a lightweight action with no output schema, so the coverage is reasonably 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 100%, so the baseline is 3. The description adds a little extra by explaining the all:true behavior, but the schema already describes both all and drone_id clearly. The description does not materially enrich parameter understanding beyond the 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 names a specific verb ('Deploy'), a resource ('a drone'), and the transition ('from your bay into space'), which clearly distinguishes it from related siblings like load_drone, unload_drone, recall_drone, and upload_drone_script. It also states the core constraint that the drone must already be loaded.

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 gives clear usage context: the drone must be loaded, get_drones lists the bay, and upload_drone_script is the follow-up after deployment. It does not explicitly say 'do not use this when X' or name direct alternatives, but the prerequisite and post-requisite guidance effectively situates the tool in the drone lifecycle.

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