scene_find_actor

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

The readOnlyHint annotation already establishes that this is a safe search operation. The description adds useful behavioral detail beyond the annotation by specifying that Name matching is partial and TypeName matching is exact, and that the search is against serialized scene/prefab files.

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 front-loaded sentence with no filler. Every phrase contributes to identifying the target, the search criteria, or the matching semantics.

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?

An output schema exists, so return values need not be described, and readOnlyHint covers the safety profile. The description is nearly complete for this simple search tool, with the main gap being explicit routing guidance versus editor_find_actors.

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 description coverage is 0%, so the description must carry parameter meaning. It explains the matching semantics for name and typeName and identifies path as the .scene/.prefab file to search, though it does not explicitly state that name and typeName are optional or exactly how multiple criteria combine.

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 states a specific verb and resource: searching actors inside a .scene/.prefab file by Name and/or TypeName. This is clear enough to distinguish file-based search from editor-oriented siblings, though it does not explicitly name or contrast editor_find_actors.

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 file-targeted phrasing implies when this tool is appropriate, but there is no explicit guidance on when to use it instead of editor_find_actors or scene_list. It also does not state prerequisites such as whether the file must exist or be readable.

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