docker_grep

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

No annotations provided, so description must disclose behavior. It lacks details on regex flavor, case sensitivity, whether logs are fetched from all time or limited, and what happens with invalid patterns. The tail parameter implies a line limit but is not explained.

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?

Description is succinct (one sentence) but omits critical details. It is not overly wordy, but the brevity sacrifices clarity and completeness.

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?

Despite having an output schema (content unknown), the description does not explain what the tool returns. It also fails to differentiate from sibling tools like docker_logs, tail, or search, leaving the agent unsure when to use this 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 description coverage is 0%, so description should compensate. It mentions 'regex pattern' for pattern param but does not explain container (name/ID format) or tail (number of lines from end). Agents must infer from parameter names only.

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 action ('search'), resource ('Docker container logs'), and method ('regex pattern'). It is distinct from siblings like docker_errors (errors only) and docker_logs (general logs) but could be confused with 'search' tool.

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?

No guidance on when to use this tool versus alternatives. Does not specify prerequisites, when not to use, or how it compares to similar tools like docker_logs or tail.

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