get_selected_actors

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

Although no annotations are provided, the description clearly identifies the tool as a read-only getter with no side effects. The behavior is straightforward, but it doesn't elaborate on the return format or whether it returns a snapshot or live references. Given the simplicity, this is adequate.

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 of 10 words, front-loaded with the key action and resource. Every word is meaningful, and there is no redundant information.

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 zero parameters and the existence of an output schema (which handles return value documentation), the description is complete. It conveys the essential purpose and scope without needing further elaboration.

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 input schema has zero parameters and 100% schema description coverage. According to the guidelines, a 0-parameter tool receives a baseline of 4. The description adds no parameter information, which is acceptable because no parameters exist.

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 verb 'Get', the resource 'selected actors', and the scope 'in the editor viewport'. It distinguishes itself from sibling tools like 'get_selected_assets' and 'find_actors' by focusing on the current selection in the viewport.

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 the tool should be used to obtain currently selected actors, but it does not explicitly mention when to use this tool versus alternatives like 'find_actors' or 'get_actors_in_level'. No exclusions or when-not-to-use guidance is provided.

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