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

With no annotations, the description carries the full behavioral burden. It discloses a non-obvious behavior: the save blocks until pending page-source and screenshot captures finish before persisting. This is valuable context beyond the schema. It does not cover idempotency or return values, but the core synchronization behavior is clearly stated.

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 tight sentences with no filler. The main action is front-loaded, and the important waiting behavior is added in the second sentence. Every word contributes to the agent's understanding.

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?

This is a simple two-parameter save tool with no output schema, and the description covers the essential purpose and the main non-obvious timing behavior. It could add what happens if the recording is not yet complete or whether saving is irreversible, but these are not critical gaps for an agent to invoke it correctly.

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 100%, so the baseline is 3. The schema already explains that recordingId comes from flow_recording_start and that name optionally overrides the original. The description adds no additional parameter-level detail, which is acceptable given the 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?

States a specific verb ('Save'), a specific resource ('a completed recording'), and the destination ('the database'). It clearly distinguishes this from sibling tools like flow_recording_start and flow_recording_cancel. An agent can tell what it is for without opening the 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 phrase 'completed recording' implies the tool is used after recording has finished, and the waiting behavior suggests it should be called after background captures are pending. However, it does not explicitly name alternatives or state when not to use it, leaving the agent to infer the lifecycle context.

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