splunk_search

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that execution is synchronous and blocking, that count is capped by SPLUNK_MAX_RESULTS, and that offset supports pagination. However, it omits timeout behavior, permission/auth requirements, performance implications, and what happens with excessively broad searches.

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 front-loaded with the most important behavioral detail, synchronous blocking execution, before moving into parameter notes. It is compact and every clause contributes useful information.

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?

The tool is complex and has no annotations, but the description covers the core execution model, all parameters, result count limits, and pagination. Because an output schema exists, return-value documentation is not required. The main missing context is explicit routing guidance versus sibling search tools and timeout behavior.

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 description coverage is 0%, so the description must compensate, and it does: all five parameters are explained. It provides SPL and time-bound examples, clarifies that count is a maximum capped by SPLUNK_MAX_RESULTS, and identifies offset as the pagination index.

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 states a specific verb and resource: execute an SPL search. It also adds the key scope qualifier that the search is synchronous and blocking within an explicit time window. It does not explicitly differentiate this tool from siblings such as splunk_search_async, splunk_search_stream, or splunk_search_preview.

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 phrase 'synchronous blocking' and 'explicit time window' imply when this tool is appropriate, but there are no explicit when-to-use or when-not-to-use guidelines. It also does not name alternatives like async, streaming, or preview searches, which is a notable gap given the many search-related siblings.

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