Recordingstatus

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

No annotations, so the description carries the full burden. It usefully discloses the default-target behavior and that state is 'idle' when nothing is recording, and 'Return' implies a read-only operation, but it omits error behavior for an unknown/expired recordingId and any permission or rate-limit context.

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?

Three short sentences, front-loaded with what is returned, then the parameter rule, then the idle-state edge case. No filler.

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?

An output schema exists, so return values need not be enumerated, yet the description names them anyway. For a single-parameter read tool this is nearly complete; only failure modes for an invalid recordingId are missing.

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 0% and recordingId is documented only as a nullable string, so the description's rule 'omit recordingId to ask about the active recording' supplies the parameter's actual semantics. It adds real meaning the schema cannot convey, though it does not describe accepted ID formats.

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?

Specific verb (Return) plus the exact resource and its fields (recording state, duration, display, file size). It is unmistakably distinct from the sibling mutators startRecording/finishRecording/abortRecording/cleanupRecording/confirmUpload.

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?

Explicitly tells the agent when to omit recordingId (to query the active recording), which is the main usage decision for this tool. It does not state exclusions or errors, but the sibling names make the alternative operations obvious.

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