adb_result_drop

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

No annotations are provided, so the description carries full burden. It discloses that the tool deletes handles and clarifies the two conditional modes (single vs. all). It could mention error handling or persistence, but it adequately communicates the destructive nature and scope ('in this session').

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 three sentences: first states purpose, second explains the two modes with parameter conditions, third gives a use case. No filler, front-loaded, and efficiently structured.

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 few parameters, the description covers the essential behavior. It could mention return value or confirmation on success, but for a delete tool, the two modes and purpose are sufficiently 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?

The description adds significant meaning beyond the input schema. It clarifies the conditional requirement: tool and name are both needed for a single drop, while all=true drops everything. It explains the logical relationship between parameters, which is not evident from the schema alone.

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 specifies the action: delete a stored result handle or clear all handles. It distinguishes between the two modes (single vs. all), and the sibling tools (adb_result_get, adb_result_list) confirm this is the deletion tool, so it's well-differentiated.

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 when to use the tool: 'freeing up the store cap proactively or removing stale data before a sensitive operation.' It does not provide when-not-to-use or compare with alternatives, but the context is clear and sufficient for a simple deletion operation.

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