docker_grep

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

No annotations are provided, so the description carries the full burden. It discloses the exact command executed ('docker compose logs --tail=N --no-color SERVICE | grep PATTERN') and the behavior of returning only matches. It also clarifies accepted formats for since/until, adding useful context beyond basic purpose.

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 and well-structured: it starts with the purpose, then gives the command, then provides a comparative benefit, and ends with a parameter note. Every sentence adds value with no redundancy or filler.

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 the tool has 8 parameters, no output schema, and no annotations, the description covers the essential aspects: purpose, command behavior, returned data (only matches), and time parameter formats. It could be more complete by specifying output format or prerequisites, but it is sufficient for an agent to select and invoke the tool.

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 adds meaning by showing how parameters map to the shell command (e.g., tail=N, SERVICE, grep PATTERN) and reiterates the since/until format in a compact way. This is helpful but not extensive, meriting a 4.

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 states a clear purpose: 'Поиск по логам Docker-контейнеров на удалённом VPS' (search Docker container logs on remote VPS) and explicitly differentiates from the sibling docker_logs by noting it returns only matching lines and is more economical for targeted search. This makes the tool's function and distinction unambiguous.

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?

It provides a direct usage comparison: 'Экономичнее docker_logs для прицельного поиска — возвращает только строки с совпадением' (More economical than docker_logs for targeted search — returns only matching lines). This clearly indicates when to prefer this tool, though it does not explicitly state when not to use it or mention other siblings.

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