hermes_search_files

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=false. The description adds 'Read-only' which is redundant. It provides some context about the 'target' parameter for filenames, but does not disclose behavior beyond annotations, such as what 'allowed' means or any restrictions on file access.

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 consists of two concise sentences that are front-loaded with the core purpose. It efficiently conveys the tool's action and a key parameter hint without unnecessary details. Minor improvement could be moving the 'Read-only' annotation to the first sentence.

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?

With 5 parameters (only 1 required) and an output schema present, the description covers the basic purpose but lacks details about search semantics (e.g., pattern matching type), the difference between 'files' and 'path' targets, and how file_glob and limit affect results. It is minimally adequate but not fully complete for complex use cases.

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 of parameter descriptions is 0%, so the description must compensate. It only adds meaning for the 'target' parameter by suggesting values 'files' or 'path'. No explanation is given for parameters like pattern, path, file_glob, or limit, leaving the agent to rely solely on parameter names which may be ambiguous.

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 searches allowed local files on the Hermes machine, with a verb and resource. It also provides a hint about using target='files' or target='path' for filenames. It distinguishes from siblings like hermes_list_files and hermes_read_file, but could be more specific about the search mechanism (e.g., pattern matching, content search).

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 implies usage for searching files, but does not explicitly state when to use this tool versus alternatives like hermes_list_files for listing directories or hermes_read_file for reading contents. No explicit when-to-use or when-not-to-use guidance is provided, leaving the agent to infer based on the sibling tool names.

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