start_recording

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

No annotations are provided, so the description must fully disclose behavioral traits. It only states the prerequisite and the basic function. It fails to mention side effects, performance impact, or whether multiple recordings can be stacked. The brevity leaves significant gaps.

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 an important prerequisite icon. It is front-loaded with the essential information and contains no wasted words.

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 parameters, no output schema, and no annotations, the description is minimal. It covers the core purpose and a precondition, but lacks details about what the recording produces (e.g., no mention of storage or stop mechanism). This might leave an agent with unanswered questions.

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?

There are zero parameters, so baseline is 4. The description adds no parameter information, but it is unnecessary. The prerequisite about the game state is relevant context, not parameter semantics.

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 specifies the verb 'Start' and the resource 'recording game state changes', clearly indicating the tool's function. The prerequisite 'Game must be running' adds clarity. It distinguishes itself from sibling tools like stop_recording and record_gameplay.

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 includes a clear prerequisite for usage ('Game must be running') but does not explicitly state when not to use this tool or mention alternatives. The context from sibling tools implies the appropriate scenario, making it mostly clear.

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