ssh_grep

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

With no annotations, the description carries the burden of behavioral disclosure. It reveals regex flavor (PCRE-like -P fallback to POSIX ERE), directory skipping (.git/.hg/.svn), and default output mode. This adds meaningful context beyond the schema, though it omits details like SSH authentication behavior or error handling.

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?

Two sentences, tightly packed with essential information. Front-loaded with purpose, then key behavioral traits. No filler or redundancy; every clause earns its place.

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?

For a 16-parameter tool with no output schema and no annotations, the description covers the core behavior well: purpose, regex variant, recursion behavior, and output modes. It does not elaborate on SSH-specific parameters like identity_file or strict_host_key_checking, but those are adequately described in the schema and are secondary to the tool's core function.

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 81%, so the baseline is 3. The description goes beyond the schema by explaining regex semantics (PCRE vs POSIX), the meaning of 'path' recursion and skipped directories, and the default output mode. These details help the agent understand parameter behavior more deeply.

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's function: 'Search remote file contents over SSH'. It distinguishes itself as 'the remote counterpart of the local content-search tool', making its role unambiguous and differentiating it from sibling tools like ssh_glob.

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?

Provides clear context that this is the remote search counterpart, implying use when remote content search is needed. Offers in-tool guidance about defaulting to files_with_matches for efficiency and using content mode for line details. However, it does not explicitly exclude alternatives or mention when not to use this tool.

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