hayabusa_search

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

No annotations and no disclosure of behavioral traits like read-only nature, error handling, or performance implications beyond basic search function.

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?

Concise and well-structured: one-line summary followed by bulleted args. No extraneous text, though slightly more context on behavior could fit.

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?

Covers all parameters but lacks output description, error handling, or performance notes. Adequate for a simple search tool given no annotations or output schema.

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?

With 0% schema description coverage, the Args section explains all four parameters (target, keywords, regex, max_rows) with clear semantics and defaults, adding value.

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?

Clear verb ('search') and specific resource ('.evtx event records') with differentiation from sibling tools focused on logon summaries or rule scanning.

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 on when to use this tool vs alternatives (e.g., scan_evtx, hayabusa_logon_summary) or what contexts are appropriate.

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