search_events

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

With no annotations, the description must carry behavioral disclosure. It does reveal the search scope (name/description) and available filters, which is useful. However, it does not mention the return format, pagination, default limits, or that the operation is read-only, leaving a moderate transparency gap.

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 two short sentences with no filler. The primary action is front-loaded, and the filter options are compactly summarized. Every word contributes meaning.

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 the parameters, and the description covers the search scope and filters. However, there is no output schema or annotation, and the description does not indicate what kind of results are returned or suggest following up with get_event_detail for full event information. An agent can invoke the tool correctly but may not know what to expect in the response.

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 baseline is 3. The description essentially restates what the schema already covers (query by name/keyword, filter by bus/loader) without adding new format, syntax, or constraint details. It provides a useful high-level summary but no additional semantic value beyond the schema.

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 ('Search') and resource ('Forge/NeoForge events'), and clarifies that the search targets name or description with optional filters. This distinguishes it from sibling tools like search_api and search_docs, which target different resource types, and from get_event_detail, which retrieves a single event rather than searching.

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 gives clear context for when to use the tool: finding events by name/description, with optional bus and loader filters. It does not explicitly list exclusions or mention a more specific sibling like get_event_detail for retrieving full event details, so it falls short of a 5 but still provides enough situational guidance.

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