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

With no annotations, the description carries the full burden. It usefully discloses sort order (newest first) and the pagination mechanism (cursor for the next page), but says nothing about permissions, whether reads are safe/non-mutating (only implied by "List"), default limits, or what a page of results contains.

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 sentences, front-loaded with the core action and ordering, then filter/pagination details. Dense but every clause is relevant, though the q syntax explanation duplicates the schema verbatim and could be trimmed.

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 list tool with no output schema and no annotations, the description covers filtering semantics, ordering, and pagination adequately. It stops short of describing result shape or cursor-invalid behavior, which an agent might still need.

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 every parameter including q, since/until formats, and signature_valid is already documented in the schema. The description's filter list and q syntax largely restate the schema rather than adding new meaning, so baseline 3 applies.

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?

States a specific verb and resource ("List events captured by a bucket"), plus scope and ordering ("newest first"). It is clearly distinguishable from siblings like latest_event, get_event, and wait_for_event without opening any schema.

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 scope ("captured by a bucket") implies when to reach for it rather than latest_event or get_event, but no alternative tool is named and no explicit when-not guidance is given. Usage is inferable but not spelled out.

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