search_code

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

No annotations are provided, so the description carries full burden. It only states the basic action without disclosing behavior like whether script_url is optional, how results are returned, or potential side effects. This is insufficient for an agent to anticipate 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 sentence of 4 words, very concise. While front-loaded with the purpose, it is too brief to cover essential details. It could be expanded with minimal additional sentences to improve completeness without losing conciseness.

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 5 parameters, no output schema, and no annotations, the description is completely inadequate. It does not explain what 'loaded scripts' means, how to use optional parameters, what the output format is, or any behavior beyond the basic search action.

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%, and the description adds no parameter information. While parameter names and defaults are somewhat self-explanatory (keyword, script_url, max_results, context_chars, context_lines), the description does not clarify their role or relationship, leaving the agent to infer from names alone.

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 'Search keyword in loaded scripts' clearly states the action (search), resource (loaded scripts), and implies the search term (keyword). It distinguishes from sibling tools like 'scripts' which likely list scripts, not search within them.

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 vs alternatives, such as using 'scripts' to list scripts first or other search tools. The description implies it works on already loaded scripts but does not specify prerequisites or exclusions.

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