get_actors_in_level

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

Without annotations, the description carries the full burden. It correctly states it returns data for all actors (no mention of destructive behavior) but does not disclose potential performance impact of returning many actors or that it reads from the active editor world. Adequate but not richly transparent.

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-load main purpose and optional filter. No redundant words. Perfectly concise 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?

For a simple tool with one optional param and no output schema, the description is sufficient. It covers scope, return fields, and filter. Could be enhanced with guidance on when to use this vs siblings, but overall complete enough.

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% with one parameter described. The description adds 'Optional' but does not add meaning beyond the schema's 'Substring filter on actor label'. Baseline 3 is appropriate.

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 it returns name/class/transform for every actor in the active editor world, with an optional name filter. This distinguishes it from siblings like 'find_actors_by_class' (returns references by class) and 'get_selected_actors' (only selected).

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 implies usage for listing all actors with optional name filter but does not explicitly mention when to use this tool over alternatives like 'find_actors_by_class' for class-based search or 'get_selected_actors' for working with selections. No when-not-to-use guidance.

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