obs-get-record-status

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

No annotations are provided, so the description carries full burden. It mentions 'Gets', implying a read-only operation, but doesn't disclose behavioral traits such as whether it requires specific permissions, returns real-time or cached data, or has rate limits. The description is minimal and lacks context beyond the basic action.

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 with no wasted words, making it appropriately concise. However, it could be more front-loaded with additional context, but given the simplicity, it's efficient and well-structured.

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 no annotations, no output schema, and a simple tool with 0 parameters, the description is incomplete. It doesn't explain what 'status' includes (e.g., boolean, object, error states) or behavioral aspects, leaving gaps for an AI agent to understand the tool fully. More detail on the return value or usage context would improve completeness.

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 0 parameters with 100% schema description coverage, so no parameter info is needed. The description doesn't add parameter semantics, but this is acceptable as there are no parameters to document. Baseline 4 is appropriate for zero-parameter tools.

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 'Gets the status of the record output' states a clear verb ('Gets') and resource ('record output'), but it's vague about what 'status' entails (e.g., recording state, file info, errors). It distinguishes from siblings like 'obs-get-record-directory' by focusing on status rather than location, but lacks specificity on the status type.

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?

No guidance is provided on when to use this tool versus alternatives. For example, it doesn't mention if it's for checking if recording is active, paused, or stopped, or how it relates to tools like 'obs-get-record-directory' or 'obs-get-output-status'. The description implies usage for record output status but offers no exclusions or context.

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