Buscar dentro de arquivos (grep)

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

With no annotations, the description carries the burden and does add useful behavior: it excludes .git/node_modules/dist and large binary files and states the output format. It does not mention result limits, case-insensitivity, or how regex mode is activated, but those are partly encoded in the schema defaults.

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 short sentences place the main verb, resource, output format, and key exclusions up front with no filler. Every sentence 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?

The description covers purpose, return format, and ignored files, which is adequate for a simple search tool. However, it is incomplete for an agent choosing among siblings: it lacks alternative routing, undocumented parameter semantics, and any behavior about limits or matching options beyond the schema.

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 only 40%; max, is_regex, and ignore_case have no schema descriptions, and the tool description does not explain them. It only reinforces regex support and workspace scope, adding little parameter-level meaning beyond the schema's existing query/path descriptions.

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 names a specific action ('Procura texto/regex dentro dos arquivos do workspace') and the concrete return format ('arquivo:linha: trecho'), which is clear. It does not explicitly contrast with sibling search_files, though the title's '(grep)' and 'dentro dos arquivos' make the content-search intent clear.

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 statement explains when to choose this tool over search_files, list_dir, or read_file. The only usage signal is the implicit grep-style purpose; there are no exclusions or alternative tool recommendations.

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