script_grep

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

With no annotations provided, the description carries the full burden. It does convey that the operation is a search (non-mutating), that it spans all scripts, and that results include line-number snippets. However, it does not disclose whether the pattern is regex, whether there are performance or size limits, or explicitly confirm that no modifications occur.

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?

One concise sentence front-loads the operational purpose and key output detail. The 'Official Roblox Studio' prefix is lightly informational but adds little functional value; otherwise the structure is tight and efficient.

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?

For a simple two-parameter tool, the description plus the fully covered schema covers basic invocations. Still, without an output schema or notes on search syntax, matching behavior, or how this differs from sibling search tools, the overall context is adequate but not complete.

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 100%, so the baseline is 3. The description adds context about searching for symbols/definitions/patterns and returning snippets, but it does not meaningfully enrich the schema's brief 'Search pattern' and 'Scope service or folder' 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 clearly identifies the verb ('Searches'), the resource ('across all scripts'), and the kinds of matches ('symbols, function definitions, or patterns') along with the output format ('line number snippets'). It does not explicitly differentiate among the sibling search tools such as script_search or script_search_code, so it stops short of a 5.

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?

The description gives no guidance on when to use this tool versus alternatives like script_search or script_search_code. There are no exclusions, prerequisites, or hints about preferred use cases, leaving the agent to infer when this specific search tool is appropriate.

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