obs-create-record-chapter

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It indicates a write operation ('Adds'), but fails to detail critical aspects like permissions needed, whether the action is reversible, potential side effects on the recording, or error conditions. This leaves significant gaps in understanding the tool's behavior 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, clear sentence that directly states the tool's purpose without unnecessary words. It is front-loaded and efficiently communicates the core action, making it easy to parse and understand quickly, which aligns well with best practices for conciseness.

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 the tool has no annotations, no output schema, and a simple parameter schema, the description is minimally adequate but incomplete. It covers the basic action but lacks details on behavioral traits, usage context, and output expectations. For a mutation tool with zero annotation coverage, more context would be beneficial to fully guide an agent.

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%, with the single parameter 'chapterName' fully documented in the schema. The description doesn't add any extra semantic context about the parameter, such as naming conventions or constraints. Given the high schema coverage, the baseline score of 3 is appropriate as the schema handles the parameter documentation adequately.

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 clearly states the action ('Adds') and target resource ('new chapter marker to the file currently being recorded'), making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like 'obs-split-record-file' or 'obs-create-scene', which might also involve recording or creation operations, leaving room for slight ambiguity in sibling context.

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 provides minimal usage guidance by implying the tool should be used when recording is active ('file currently being recorded'), but it lacks explicit when-to-use criteria, alternatives, or exclusions. For example, it doesn't clarify if this works only during active recording sessions or if it has prerequisites compared to other creation tools in the list.

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