adb_result_list

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

With no annotations, description fully discloses behavior: lists all handles in session, read-only, metadata fields, scoped per-auth-token, survives server restart within TTL. No hidden side effects mentioned.

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?

Three sentences, front-loaded with purpose, no redundant words. Each sentence adds value: purpose, return info, usage guidance, behavioral details.

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?

Complete for a no-parameter listing tool. Covers purpose, return metadata, integration with other tools, and behavioral scoping/TTL. No gaps given the simplicity.

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 has zero parameters with 100% coverage. Description adds value by confirming no filtering needed and explaining what listing all handles entails. Baseline 4, but description compensates with context.

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?

Clearly states 'List all result handles currently stored in this session' with specific verb and resource. Distinguishes from siblings like adb_result_get (retrieves content) and adb_result_drop (deletes). Specifies metadata fields returned.

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?

Explicitly tells how to use results with adb_result_get or MCP Resources to retrieve content. Provides context on scoping and TTL survival. Implicitly when to use: when you need an overview of stored handles.

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