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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds ordering ('newest first') and pagination ('Pages with cursor'), but omits result caps, cost/rate behavior, and how defaults expand scope when filters are omitted — details that matter for a 10-parameter search.

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 very long, comma-piled sentences with no front-loaded list of what matters. The phrase 'in the title, culprit or message' is stated twice — once in the opening scope enumeration and again inside the q explanation — which is pure duplication.

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?

For a 10-parameter, no-required-args search with no output schema, the description covers filtering vocabulary, defaults (partly via schema), and pagination, but never describes the returned event shape and gives no guidance on combining q with structured filters. Adequate, with clear 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?

Schema coverage is 100%, so the baseline is 3, but the description meaningfully exceeds it by spelling out the q grammar (phrases, /regex/, level:, category:, field:value, -term, !key:value, a OR b, key:[a, b], wildcards, key:>500, has:key) that the schema only points at via a docs URL. It falls short of 5 because it never explains whether q composes with or overrides the structured filters like level, category, and fields.

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 names a concrete resource (events) with scope (environment, range, levels, categories, fields, text), so an agent can tell this is a filtered event search. However, it never names or contrasts the nearest siblings (get_event for a single event, list_issue_events for an issue's event stream), leaving the 'Explore' framing as the only differentiator.

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?

Usage is only implied by the enumeration of filters; there is no statement of when to reach for this tool versus get_event or list_issue_events, and no note on how the free-text q interacts with the structured filters. The reader must infer the triage-style search intent.

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