Bulk Sigma Rule Lookup

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

Annotations already indicate readOnly and idempotent, but the description adds critical behavioral details: per-item error handling (status per ID), quota consumption (1 unit per rule_id, hourly limits), batch cap of 50, and rate limit handling (skipped_due_to_rate_limit). No contradictions.

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 efficient and well-structured: first sentence gives core purpose, then use case, then output shape, then quota details. Every sentence adds unique value without redundancy.

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 the tool's single parameter, rich annotations, and output schema, the description covers all necessary aspects: purpose, usage context, quota semantics, error handling, and batch behavior. No gaps.

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?

The input schema covers 100% of parameters (only rule_ids), but the description significantly enhances understanding: adds max 50 items, RFC 4122 format, quota counting per ID, and per-item validation outcomes (invalid_format, not_found).

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 does a bulk lookup of Sigma rules by UUIDs, retrieving full records for up to 50 IDs in a single call. It explicitly differentiates from the sibling sigma_rule_lookup by noting the bulk capability.

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 provides explicit guidance: 'Designed for triage workflows where multiple rule ids are known (e.g., from a SIEM alert batch or a tagged detection bundle)' and contrasts with N separate sigma_rule_lookup calls.

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