search_in_scripts

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

Annotations already declare readOnlyHint=true, which covers safety. The description adds that the search is regex-based and targets a 'collected script cache', clarifying the data source. However, it does not disclose details about limit/maxTotalSize behavior or search semantics beyond the annotations.

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 core purpose. Every word contributes, with no redundancy or filler.

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?

With no output schema and only 0% parameter descriptions, the description leaves significant gaps. It does not explain what 'collected script cache' means, how limit and maxTotalSize affect results, or what the return format looks like. This could confuse an agent on expected behavior.

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 0%, so the description must compensate. It explains that 'pattern' is a regex, but says nothing about 'limit' or 'maxTotalSize', leaving their semantics ambiguous. The parameter names are somewhat self-explanatory, but the description does not provide sufficient detail for a low-coverage schema.

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 tool's function: searching in a collected script cache using a regex pattern. It specifies the resource (script cache) and the action (search with regex), which distinguishes it from sibling tools like search_in_sources (which likely searches source files directly).

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 implies usage when one needs to search within collected scripts using regex, but it does not explicitly state when to use this tool over alternatives like search_in_sources. No exclusions or alternative tool mentions are provided.

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