recording_capture

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

No annotations are present, so the description carries the behavioral transparency burden. It only states the capture action and does not disclose side effects, failure behavior, session requirements, or what happens if the session is not active. It is not misleading, but it is too thin to be behaviorally transparent.

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 front-loaded sentence with no filler or redundancy. It earns concision credit, though the brevity is partly due to under-specification rather than deliberate shaping.

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 that there are no annotations, three parameters at 0% schema coverage, and an unexplained required 'action', the description is not complete enough for correct invocation. The output schema exists, but the missing parameter semantics and usage context leave significant gaps.

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%, and the description adds no meaning to the three parameters. The required 'action' string has no documented accepted values or enums, and 'session_id' and 'note' are unexplained, so an agent cannot reliably construct a valid invocation.

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 uses a specific verb and resource: 'capture a screenshot/slide in the active recording session.' It is mostly clear and distinguishes itself from a general screenshot tool by anchoring the capture to a recording session, though it does not explicitly name sibling alternatives like 'screenshot.'

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 use during an active recording session but gives no explicit when-to-use guidance or alternatives. Sibling tools include 'screenshot', 'recording_start', and 'recording_stop', yet the description never helps an agent choose between them or state prerequisites such as starting a recording first.

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