suricata_query_alerts

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

No annotations provided; description carries full burden. States it's a search/filter but doesn't mention read-only nature, authentication needs, data source specifics (e.g., eve.json file location), or performance implications. Missing safety context.

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?

Two sentences, front-loaded with action and data source. Every sentence adds value: first defines scope, second lists filters and return characteristic. No wasted words.

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?

Describes basic behavior (search filters, return most recent) but lacks details on default behavior with no filters, output format, or pagination. For a 10-param tool with no output schema, more context on expected results would be helpful.

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 covers all 10 parameters (100% coverage). Description restates filters but adds no new meaning beyond what schema provides (e.g., format, constraints, interaction). Baseline 3 applies.

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?

Clearly states it searches Suricata alerts from eve.json, lists filters (signature, severity, IP, protocol, time), and says returns most recent. Distinguishes from siblings like suricata_alert_summary (aggregated) and suricata_eve_stats.

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 when-to-use or when-not-to-use guidance. Does not mention alternatives or exclusions. Usage context must be inferred from sibling names.

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