search_scripts

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

With no annotations, the description should fully disclose behavioral traits. It only mentions 'cached script sources' but does not specify performance implications, whether searches are case-insensitive (though a parameter exists), how pagination works, or whether dynamic scripts are included. This lack of detail impairs the agent's ability to predict tool 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?

The description is a single, concise sentence that conveys the core purpose without wasted words. However, it could benefit from additional structure to include key details about parameters and usage.

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 complexity of 6 parameters and no output schema or annotations, the description is insufficiently complete. It does not explain the result format, pagination behavior, or what 'context_lines' does, leaving significant gaps for the 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?

Schema description coverage is only 17% (only 'filter' has a description). The description adds no additional parameter clarification beyond 'by text or regular expression' which maps to 'query' and 'regex'. Parameters like 'max_results', 'context_lines', and 'case_sensitive' are left unexplained, despite low schema coverage.

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?

Description clearly states the tool searches cached script sources by text or regular expression. It uses specific verbs ('search') and resources ('cached script sources') and distinguishes from sibling tools like 'list_scripts' and 'get_script_source' which serve different purposes.

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 the tool is for searching script content, but does not explicitly state when to use it over alternatives, nor does it provide guidance on prerequisites or limitations. Usage context is left entirely to the agent's inference.

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