Search indexed scripts

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds the 'private' and 'in-memory' qualifiers, which imply a session-local index that likely must be populated first, but it doesn't elaborate on availability or result 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 with no filler. It front-loads the action and scope, making it concise and efficiently structured.

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 no parameter descriptions for query/className/maxResults, the description should explain search semantics and usage prerequisites. It mentions searchable fields but doesn't clarify query syntax, default behavior, or the need to run index_scripts first, leaving gaps for a 4-parameter tool.

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 coverage is only 25% (only clientId has a description). The description adds that search is by path/name/class/hash, which suggests query is a general search field, but it doesn't explain how className relates to query or the role of clientId and maxResults. This partially compensates for the 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?

The description uses a specific verb 'Search' with a clear resource ('private in-memory script index') and lists searchable attributes (path/name/class/hash). This differentiates it from sibling tools like analyze_script or disassemble_script, which operate on indexed scripts rather than searching 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?

The description clearly implies when to use the tool: when you need to find scripts in the in-memory index by path/name/class/hash. However, it does not explicitly state when not to use it or mention alternatives, though the context is sufficiently clear.

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