adb_find

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

Without annotations, the description carries the burden. It mentions result capping (maxResults) and truncation reporting, and glob matching. However, it lacks details on performance (e.g., can be slow on large trees), root requirement for system paths, and the exact meaning of 'reports truncation'. A more explicit statement about output would help.

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 short, focused sentences. First states purpose, second explains method and constraints, third mentions additional behavior. No filler or redundancy.

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 7 parameters and no output schema or annotations, the description covers the core behavior: search method, glob matching, result capping, truncation reporting. It misses minor details like output format or error handling, but is otherwise complete for an AI agent to use correctly.

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. The description reinforces the use of glob patterns and result capping but adds little beyond the parameter descriptions in the schema. For example, it doesn't explain the interplay between maxDepth and searchPath or clarify that searchPath defaults to /sdcard.

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 it searches for files on the device by name or pattern using glob matching. The verb 'search' and resource 'files on the device' are specific and distinguish it from related tools like adb_ls (list directory) and adb_file_stat (stat a file).

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 explains the tool's function but does not explicitly state when to use it versus alternatives like adb_ls or adb_grep. No 'when to use' or 'when not to use' guidance is provided, leaving the agent to infer from context.

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