find_actors_by_class

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

With no annotations, the description explains the matching logic (case-insensitive, path stripping) and notes it composes get_actors_in_level. It implies a read-only operation, though not explicitly stated. The behavioral details are adequate for a non-destructive filter.

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?

Three concise sentences, each adding essential information. The purpose is front-loaded, and there is no redundancy or extraneous content.

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?

While parameters are well-covered, the description omits the return type or format of the results. As a filter tool with no output schema, this is a notable gap. The behavior is simple, but completeness suffers from missing output description.

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%, providing a baseline of 3. The description adds value by clarifying that class_name accepts short names or paths, explaining case-insensitivity and path-stripping behavior, which surpasses the schema's description.

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 tool filters actors by class, distinguishes it from get_actors_in_level by specifying it composes that tool and matches class names, and provides concrete use cases like 'find every light'.

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 explicitly contrasts with get_actors_in_level, advising against using it to dump all actors. It gives specific scenarios (finding lights/spawn points). However, it doesn't mention other filtering alternatives or when not to use it.

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