reverse_read_live_entries

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

With no annotations, the description must disclose behavioral traits. It mentions snapshotting and advancing the cursor, which implies side effects, but does not state whether entries are returned, whether the operation is destructive, or what happens to the cursor after calling. The output schema exists but the description does not reference it or clarify the return behavior.

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, concise sentence that front-loads the primary actions (snapshot and advance). It is efficient with no wasted words, though it could benefit from a second sentence about parameters or behavior.

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 tool has 7 parameters, no annotations, and an output schema, the description is incomplete. It does not explain the meaning of 'live cursor' or how 'consume new entries' relates to the output, nor does it mention that filters apply. An agent cannot fully understand the tool's behavior or invocation context from this description alone.

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 14% (only snapshot_format has a description). The tool description does not explain any parameters, such as filters like method_in, status_in, host_contains, path_contains, or the meaning of limit. It adds no value beyond the parameter names themselves, which is insufficient given the low schema coverage.

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 action: snapshot the Charles session and advance the live cursor to consume new entries. It clearly distinguishes from reverse_peek_live_entries which likely peeks without consuming, and from other read tools. It does not mention filtering parameters but the core purpose is clear.

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 given on when to use this tool versus alternatives. It does not mention that this should be used instead of reverse_peek_live_entries when the cursor needs to advance, nor any conditions for using filters or snapshot_format. The user must infer usage from the name and description.

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