oracle_grep

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

The description reveals the result limit of 50 matches, which is a behavioral trait. However, it does not mention other important behaviors like case sensitivity, recursion behavior, or file type filtering. Since no annotations are provided, the description carries the full burden but only partially fulfills it.

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 a single concise sentence that front-loads the purpose. Every word serves a purpose, with no unnecessary information.

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 existence of an output schema and low complexity, the description is partially complete. It mentions a result limit but omits return format details and parameter behavior, which may leave gaps for an AI agent.

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?

With 0% schema coverage, the description adds no meaning to the parameters. It does not explain the 'pattern' format or the 'path' default behavior, which is essential for correct usage. The description fails to compensate for the lack of schema documentation.

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 verb 'Search', the resource 'source files', and the action 'for a regex pattern'. It also mentions a result limit, distinguishing it from sibling tools like oracle_read or oracle_run.

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 is provided on when to use this tool versus alternatives like oracle_read or oracle_run. The description does not specify scenarios, limitations, or exclusions.

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