sonic_read_events

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

With no annotations, the description carries the full burden, but it only mentions 'buffered' and 'after an optional sequence number'. It does not disclose whether reading consumes events, whether events are ordered, or any rate-limits. This leaves key behavioral traits ambiguous for an agent.

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 redundant words. Every word adds value.

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?

While an output schema exists, the description lacks behavioral context such as whether events are removed after reading, how to use 'since' effectively, or any caveats. For a tool with no annotations and only 2 parameters, more explanation is needed for safe and effective use.

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?

The description clarifies that 'since' is a sequence number, which adds meaning beyond the schema. However, 'limit' is not mentioned, and with schema description coverage at 0%, the description does not fully compensate for both parameters.

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 reads buffered Sonic Pi events after an optional sequence number, giving a specific verb, resource, and scoping condition. It is distinct enough from siblings like sonic_get_logs or sonic_send_cue, though it does not explicitly name alternatives.

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?

No guidance is provided on when to use this tool versus others, or when not to use it. The phrase 'after an optional sequence number' implies incremental reading, but there is no explicit context for pollers or event consumers.

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