invariance_workflow_event_list

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety and non-exhaustive nature are covered. The description adds little behavioral context beyond the filterable fields; it does not disclose pagination behavior, default ordering, or the fact that openWorldHint implies partial results. For a list tool, this is a notable 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 a single, front-loaded sentence with no wasted words. It states the core action and the main filtering capability efficiently, earning full marks for conciseness and structure.

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 list tool with 11 optional parameters and no output schema, the description is minimal. It omits essential usage details like pagination (cursor handling), result limits, default ordering, and clarification of ambiguous fields. Given the openWorldHint, an agent needs guidance on how to iterate over results, which is absent.

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 only 36% (4 of 11 params have descriptions). The description names filter categories (case, workflow, tenant, actor, type, time window) which roughly map to parameters, but it does not clarify ambiguous distinctions like actor_id vs actor_type vs end_user_id, or what workflow_key vs workflow means. It partially compensates but leaves several parameters under-documented.

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 ('List') and resource ('semantic workflow events') with a scope ('across cases'), which is clear. However, it does not explicitly differentiate from sibling tools like invariance_case_events_list or invariance_workflow_observability_list, so an agent might not immediately know which is the right choice.

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 lists available filter dimensions (case, workflow, tenant, actor, type, time window), giving some sense of when this tool is appropriate for cross-case queries. However, it offers no explicit guidance on when to prefer this over alternative list tools, no exclusions, and no mention of prerequisites or context.

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