ssh_find_files

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

No annotations are provided, so the description carries full burden. It explains the purpose and parameters but does not disclose behavioral traits such as read-only nature, permission requirements, connection prerequisites, or error handling. The tool is implied to be safe, but not explicitly stated.

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 concise, using a clear docstring format with bullet-pointed Args section. Each parameter gets a line, and the overall length is appropriate. Could be slightly more terse, but structure is effective.

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 6 parameters, 0% schema coverage, and no output schema, the description adequately covers parameter semantics but lacks details on return format, error handling, and prerequisites like SSH connection setup. It is minimally complete for an agent to use, but gaps remain.

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 description coverage is 0%, so the description compensates well by explaining each parameter with examples (e.g., pattern: '*.py'), accepted values (file_type: 'f', 'd', ''), and defaults. It adds meaning beyond the schema's titles and types.

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 'Find files by name pattern on the remote server,' providing a specific verb ('Find'), resource ('files'), and scope ('by name pattern'). This distinguishes it from sibling tools like ssh_list_dir (lists directory without pattern) and ssh_grep (searches file contents).

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 lists parameters and their defaults, which implicitly guides usage, but it does not explicitly state when to use this tool over alternatives like ssh_list_dir or ssh_grep. No when-not-to-use or exclusion criteria are provided.

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