update_drone

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

The description explains the partial update behavior (omitted fields unchanged), which is a key trait. However, it lacks information about return value, error handling, or any side effects, and no annotations are provided to supplement this.

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?

Two short, direct sentences with no fluff. The purpose is stated first, followed by a key usage guideline. Every sentence earns its place.

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?

The description covers the core functionality and key parameter behavior. It lacks information about the output/return value, but given the 100% schema coverage and the tool's simplicity, it is mostly 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 description coverage is 100%, and the description adds meaningful context about partial updates, which goes beyond the schema. It clarifies that only provided fields are modified, adding value for parameter usage.

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 action ('Update') and the resource ('existing drone profile'). It differentiates from sibling tools like create_drone and delete_drone by specifying it's an update operation.

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 explicitly states to 'Pass only the fields you want to change' and advises using list_drones to find drone IDs. It provides clear context but does not explicitly mention when not to use the tool, though the sibling list implies alternatives.

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