reverse_charles_recording_status

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It says 'Inspect' which implies a read-only operation, but it does not disclose what the returned status contains, whether the optional live_session_id changes the response shape, or whether any side effects occur. The description adds minimal behavioral context beyond the verb.

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 purpose and appends the optional scope. No wasted words, though it could have used the space to add parameter semantics.

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 an output schema, the return value shape is covered elsewhere, but the description still lacks guidance on when to pass live_session_id, how this differs from charles_status, and what 'reverse live-session state' means. For a status-inspection tool with no annotations and one undocumented parameter, this is incomplete.

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 0%, so the description must compensate for the undocumented live_session_id parameter. The description mentions 'optional reverse live-session state' which loosely maps to the parameter, but it does not explain what values are valid, what the parameter controls, or how omitting it changes behavior. This is insufficient for a parameter with zero schema documentation.

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 ('Inspect') and resource ('Charles recording state'), and adds 'optional reverse live-session state' to distinguish it from the plain charles_status sibling. It is clear but does not explicitly name the sibling it differs from, so it loses one point.

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 implies this is the inspection counterpart to charles_status and the reverse_* live-session tools, but it does not explicitly say when to use this tool versus charles_status or reverse_peek_live_entries. The optional live_session_id hints at a conditional use case, but no explicit when/when-not guidance is given.

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