start_owned_exam_capture

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

With no annotations provided, the description carries the full behavioral burden. It usefully discloses that captured data is memory-only metadata and that navigation is user-driven in the current browser, but it omits lifecycle behavior, permissions, side effects, and what happens when the capture is started.

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 compact sentence with the main verb and resource front-loaded. It is not bloated, though it is terse enough that the semicolon clause about memory-only metadata feels slightly under-explained.

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?

For a start-capture tool in a dense ecosystem of exam-related siblings, the description is too thin. Without annotations or an output schema, it should clarify the capture lifecycle and its relationship to stop_owned_exam_capture, owned_exam_capture_status, and read_owned_exam_observation.

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 tool has zero parameters, so there are no parameter semantics to explain. Schema coverage is effectively complete by virtue of having no inputs, making the baseline score 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 provides a specific verb and resource: monitor user-driven exam navigation in the current browser. It is clear what the tool does, but it does not differentiate itself from closely named siblings such as inspect_owned_exam_navigation, owned_exam_capture_status, or read_owned_exam_observation.

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 gives no explicit guidance on when to use this tool versus alternatives. It implies use during user-driven exam navigation in the current browser, but does not mention predecessor/successor tools like stop_owned_exam_capture or owned_exam_capture_status.

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