editor_find_actors

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

readOnlyHint=true already establishes the safety profile, and the description adds real value beyond it: which scene is searched during play mode, that types match by full or short name, what fields come back, and that Truncated signals the limit was exceeded. It does not mention ordering of results or behavior with multiple loaded scenes, but the core behavior is well disclosed.

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 tight sentences, with the search scope and optional-combination rule front-loaded before the return-value note. The return explanation is somewhat redundant given the tool has an output schema, which keeps this from a 5.

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 read-only filter tool with a full schema and an output schema, the description covers scope, filter combination, type-name flexibility, and truncation. Missing only edge-case behavior such as which scene wins when several are loaded, which the agent would likely need in practice.

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%, so the baseline is 3; the description raises it by explaining that the filters are optional and combined, and that type strings accept either full or short names. The only gap is that limit semantics are left entirely to the schema.

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?

States a specific verb and resource (finds actors) plus the search scope (loaded scenes, the play-time scene during play) and the filter dimensions. It does not name or contrast with the close sibling scene_find_actor, so an agent still has to infer which search tool to pick.

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?

"all optional and combined" tells the agent that filters are conjunctive and that an unfiltered call is valid, which is useful implied usage guidance. However there is no explicit when-to-use/when-not-to-use statement and no routing to the alternative scene_find_actor or scene_outline tools.

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