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

With only readOnlyHint=false, the description carries the full behavioral burden and delivers: scripts run once per tick, first matching IF branch executes, MOVE stays within system, ATTACK starts/joins battles, DEPOSIT unloads to station storage, drone_control stat bonuses, and empty script clears. These side effects and constraints are crucial for correct invocation.

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?

Front-loads the core action in the first clause, then packs necessary scripting semantics into a single parenthetical. It is dense but every clause adds actionable information; a bulleted layout would improve scanability but not substance.

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 no output schema and minimal annotations, the description provides a thorough behavioral picture—script execution model, command constraints, clearing mechanism, and stat bonuses. It omits return values and error handling, but these are minor for a mutation tool with a clear success/failure model.

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 baseline is 3, but the description adds substantial meaning for the 'script' parameter by explaining DroneLang syntax and command behavior, which helps the agent construct valid input. No extra detail is given for drone_id or session_id 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?

States a specific verb (Upload) and resource (DroneLang script to an autonomous drone). The scope is clear and implicitly distinct from sibling drone-management tools like deploy_drone or load_drone, though it does not explicitly name an alternative.

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 operational guidance for the script content (e.g., 'Pass empty script to clear', command semantics) but never states when to choose this tool over alternatives like load_drone or recall_drone. Usage is implied by the purpose, not explicitly framed.

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