ouroboros_query_events

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the tool 'Returns a list of events matching the specified criteria,' which is minimal. It does not mention pagination behavior, ordering, potential side effects, or that omitting session_id returns events across all sessions—though the schema hints at that. This is a significant 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 a single, succinct sentence: 'Query the event history for an Ouroboros session. Returns a list of events matching the specified criteria.' It is front-loaded with the main action and contains zero fluff. Every word earns its place.

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?

Given the moderate complexity (4 params, no output schema, no annotations), the description is too thin. It lacks essential context such as the meaning of limit/offset defaults, any explanation of event types, and the fact that session_id is optional (despite implying a session is required). No output schema exists to clarify return values, so the description should have provided more detail.

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 adds no extra parameter semantics beyond the schema; it merely refers to 'specified criteria' without explaining any parameter syntax or additional meaning. The schema already documents limit, offset, event_type, and session_id, so no deduction is needed, but no enhancement is provided either.

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 clearly states the tool 'Query the event history for an Ouroboros session' and that it 'Returns a list of events matching the specified criteria.' This is a specific verb+resource pair. It does not explicitly distinguish itself from siblings, but its focus on event history makes it distinct from other Ouroboros tools like query_projection or session_status.

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 implied: this tool should be used when you need to query event history. However, there are no explicit when-to-use vs alternatives, nor any exclusions or comparisons to sibling tools. The description provides no guidance on when to use this tool over others.

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