misp_search_events

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

No annotations provided, so description carries full burden. It does not disclose behavioral traits such as read-only nature, pagination behavior, default limits, authentication requirements, or rate limits. The tool name implies 'search' but safety and side effects are not confirmed.

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?

Single sentence efficiently conveys the tool's purpose and supported search criteria. No extraneous information; every word earns its place.

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?

Despite 12 optional parameters and no output schema, the description is minimal. It lacks details on return value format, pagination, default results count (50 per schema), or practical usage examples. Incomplete for a tool of this complexity.

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?

Input schema has 100% coverage with descriptions for all 12 parameters. The description adds a concise summary grouping parameters into high-level categories (IOC value, type, tags, etc.), but does not provide additional meaning beyond the schema. Baseline is 3 for high 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 verb 'Search' and resource 'MISP events' and lists search criteria (IOC value, type, tags, date range, organization). It distinguishes from sibling tools like misp_search_attributes (searches attributes) and misp_get_event (specific event). However, it does not explicitly differentiate from misp_search_by_tag or other similar tools.

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 explicit guidance on when to use this tool versus alternatives like misp_search_attributes or misp_get_event. The description does not mention when not to use it or provide usage context beyond its basic function.

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