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

No annotations provided, so description carries full burden. It only states basic functionality without explaining important details like resource usage, file output, or what happens if called multiple times. The behavioral aspects are opaque.

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 brief and front-loads the purpose. However, the example line is somewhat redundant with the first sentence and adds little value, slightly reducing 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 presence of an output schema and a single parameter, the description leaves many gaps: it doesn't explain what a 'movie' entails, how to access the recording, or the effect of supersample. It meets only the minimal requirement.

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 description does not mention the 'supersample' parameter at all, and schema description coverage is 0%. The example shows calling with no arguments, leaving the agent without understanding what this parameter controls or how to set it.

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 tool starts recording a movie of the ChimeraX session. It distinguishes itself from sibling tools like stop_recording and take_snapshot, but does not explicitly differentiate from record_spin, which might cause confusion.

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?

Provides explicit guidance: call before making visual changes and stop_recording when done. This gives a clear usage pattern, though it doesn't discuss alternatives or when not to use this tool.

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