create_summit_gather_drone_v1

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

No annotations exist, so the description must disclose behavioral traits. It only states the tool 'builds' a robot, but fails to explain any side effects (e.g., does it overwrite an existing object?), dependencies, or required permissions. The parameter 'clear_existing' hints at potential mutation behavior but is not explained.

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, which is concise, but it sacrifices necessary detail and structure. Important information about the parameter and usage context is missing, making the conciseness detrimental to clarity.

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?

While the tool has an output schema (reducing the need to explain returns), the description fails to provide context for the single parameter. For a tool with one configurable option, more completeness is expected to ensure correct invocation.

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?

The input schema has one boolean parameter 'clear_existing' with 0% description coverage, yet the tool description does not mention or explain it. The agent cannot determine what 'clear_existing' controls or how setting it true/false affects behavior.

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 tool builds a specific robot ('Robot Gather Drone V1') with defining characteristics ('square hover harvester with suction (idle/harvest)'). It uses the specific verb 'Build' and the resource name, distinguishing it from sibling tools like create_summit_bobcat or create_summit_jaguar_afv_v1.

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?

No guidance is provided on when to use this tool versus the many sibling creation tools. The agent has no context for selecting this tool over alternatives, nor any prerequisites or conditions for calling it.

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