search_requests

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

With no annotations, the description carries the full behavioral disclosure burden, but it only states the filtering capability. It does not mention authentication prerequisites, pagination behavior, read-only nature, or the shape of returned results, all of which are relevant given the many auth and pagination parameters.

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 a single sentence with no filler, and the key verb and filter dimensions are front-loaded. Every word contributes to stating the core function.

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 schema fully documents parameters, which helps, but the lack of an output schema and annotations leaves gaps around return value shape and auth flow. The description is adequate for a basic search call but does not fully prepare an agent for behavior beyond filtering.

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 100%, so the input schema already documents all 11 parameters. The description merely recaps a few of those filters without adding extra meaning, format details, or relationships between parameters.

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 the operation ('Search requests') and the resource ('requests') with a concrete set of filter dimensions: controller, URI, status, or duration. It is clear and specific, but it does not explicitly distinguish this tool from siblings like list_requests, get_request, or get_latest_request.

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 filter list implies this tool is for finding requests by criteria, so an agent gets a reasonable hint about when to use it. However, there is no explicit guidance about when to prefer search_requests over list_requests or get_latest_request, and no exclusions or conditions are provided.

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