grep

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

Description states 'Search' (implying a read-only operation), but annotations set readOnlyHint to false, contradicting the described behavior. This inconsistency misleads about whether the tool could modify files.

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?

Single sentence with 4 words is extremely concise and front-loaded. However, it omits optional details like regex syntax, flags, and output behavior that would improve agent understanding without adding much length.

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's simplicity, the description fails to specify important behavioral aspects such as regex flavor, output format (line numbers, highlighting), and default behavior (whole file vs line-by-line). No output schema further reduces completeness.

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?

Input schema covers both parameters (pattern, file) with descriptions, achieving 100% coverage. The description adds no additional meaning beyond what the schema already provides, so baseline score applies.

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?

Description clearly states the action ('Search for patterns') and resource ('files'), providing a specific verb+resource pair. However, it does not differentiate from sibling tools like cat, head, or test_regex that may also involve file content inspection.

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 grep versus alternatives such as cat, head, or test_regex. No mention of commonly used options like recursion, case sensitivity, or output format, leaving usage ambiguous.

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