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

Annotations declare readOnlyHint=false, indicating a write operation, which the description implicitly confirms. Beyond that, the description discloses that an empty script clears the current script, explains the execution model (run once per tick, first matching IF branch), and details command behaviors (MOVE, at(), DEPOSIT). It also notes the concurrency limit tied to drone_control skill level. This provides substantial behavioral context beyond 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 is a single sentence with a long parenthetical, but it is densely packed with necessary information. It starts with the primary purpose and then covers execution semantics, command specifics, skill level interaction, and clearing behavior. Every part contributes to correct usage, so it is appropriately concise and well-structured, though slightly dense.

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 tool that uploads a scripting language, the description covers the essential behavioral details: execution per tick, conditional branching, argument handling for MOVE and at(), DEPOSIT behavior, skill-level concurrency, and clearing. It does not describe return values or error handling, but there is no output schema, and the tool's purpose is clear. The description is sufficiently complete for an agent to understand how to invoke it 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% for all three parameters, so the baseline is 3. The description adds significant value for the 'script' parameter by explaining the DroneLang language, its syntax semantics, and that an empty string clears the script. It does not add to session_id or drone_id, but those are self-explanatory. The added context for the script parameter elevates the score.

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 (upload) and resource (DroneLang script to an autonomous drone), and elaborates on the scripting language's execution semantics. This distinguishes it from sibling tools like deploy_drone, recall_drone, or load_drone, which have different purposes. The purpose is unambiguous and specific.

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 explains how the script behaves and mentions clearing with an empty script, but it does not explicitly compare with alternatives or state when to use this tool versus other drone-related tools (e.g., deploy_drone, load_drone). The usage is implied through the purpose, but there is no explicit guidance on selecting this tool over siblings.

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