script_search

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

With no annotations, the description carries the burden. It discloses the non-mutating search scope (all Luau scripts) and the regex/literal modes, which is useful context. However, it does not mention return format, match limits, or failure behavior.

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 front-loaded sentence with minimal waste. 'Official Roblox Studio' is slightly decorative but not harmful, and the core behavior is stated immediately.

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?

Adequate for a simple read-only search tool, and the schema covers all parameters well. However, with no output schema and many similarly named siblings, the description would benefit from noting what a match result looks like and how this tool differs from script_grep or script_search_code.

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 reinforces the regex/literal interpretation of query and isRegex but adds no defaults, syntax details, or examples beyond what the schema already provides.

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?

States a specific verb and resource: performs fast regex or literal text search across all Luau scripts. Clear scope, but does not explicitly differentiate from siblings like script_grep or script_search_code.

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 choose script_search over script_grep, script_search_code, or studio_search. The description implies a general-purpose script search but gives no conditions, exclusions, or alternative selection criteria.

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