Record Session

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

With annotations already indicating write operation (readOnlyHint=false) and non-idempotency (idempotentHint=false), the description adds minimal behavioral context—it does not explain what happens if called multiple times or whether it stops a previous recording. The description text is acceptable but not enhanced beyond annotation signals.

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 sentence that is concise and front-loaded with the purpose. No unnecessary words; every part 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 tool's low complexity (one optional parameter, no required arguments, output schema exists), the description is sufficient. The term 'replay journal' could be clarified but is likely defined elsewhere; overall, the description covers the essential behavior.

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% with the parameter well-described in the schema. The description does not add further semantic detail about the parameter, so a baseline score of 3 is appropriate.

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 action ('Start recording'), the resource ('all tool calls in the current session'), and the output ('to a replay journal'). It distinguishes from siblings like 'replay_session' and 'stop_recording' which have different purposes.

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 does not provide any guidance on when to use this tool versus alternatives like 'replay_session' or 'stop_recording'. No context about prerequisites or appropriate scenarios is given.

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