bulk_focus_actors

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

Describes composition of focus_actor and get_viewport_screenshot, details the settle delay behavior (sleeps between calls, not after last), and explains the screenshot_each option. Some minor gaps like error handling, but sufficient given no annotations.

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?

Two sentences, front-loaded with action, no wasted words. Perfectly concise.

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?

Comprehensive for a bulk tool with simple parameters. Mentions output (screenshots array) but doesn't specify format when no screenshots. Minor gap, but overall adequate.

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 100%, and description adds meaningful context: max 100 entries for names, default/max for delay_ms, default false for screenshot_each, and clarifies delay timing.

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?

Clearly states it frames the viewport on each actor in a sequence, optionally capturing screenshots. Distinguishes itself from sibling tools like screenshot_actor by avoiding polling loops.

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 provides a use case ('show me each enemy / spawn / light in turn' walkthroughs) and explains why it's better than using screenshot_actor individually.

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