search_log

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

The description explains key behaviors: regex usage, case sensitivity, level filtering, and max_results limit. It does not explicitly state that the operation is read-only, but with no annotations, the description provides good transparency about the search 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 well-structured with a clear bullet-like Args list. It is efficient but could be slightly more concise; however, it earns its length by covering all parameters meaningfully.

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 that an output schema exists, the description need not explain return values. It fully covers input parameters and operation context. Could mention the log file location or that it's read-only, but overall complete.

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?

Every parameter (query, max_results, regex, case_sensitive, level) is described with its purpose, default value, and behavior. This fully compensates for the 0% schema description 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 clearly states the tool searches the Vibe runtime log (vibe.log), with specific verb 'Search' and explicit resource. It distinguishes itself from siblings like 'search' by targeting a specific log file.

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 explains what the tool does but does not explicitly state when to use it over alternatives (e.g., generic 'search' tool). It implies usage for log filtering but lacks explicit when-not or alternative references.

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