List actor classes

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

No annotations are provided, so the description must carry the full burden. It mentions running an external command ('dumpactors') but does not disclose whether it is safe, idempotent, or has side effects. No information on permissions, rate limits, or expected behavior beyond the bare action.

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 with no filler. It is efficient and directly states the purpose, though it sacrifices completeness for brevity.

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?

Despite the tool being simple, the description lacks explanation of the 'instance' parameter, usage context relative to siblings, and the nature of the structured data returned (even though an output schema exists). This leaves significant gaps for effective agent selection.

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%, and the description fails to explain the single parameter 'instance'. The schema provides type, default, and bounds, but the description adds no meaning or context for when or how to use this parameter.

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 runs `dumpactors` and returns registered DECORATE/actor classes as structured data, specifying both the verb ('Run', 'return') and the resource ('registered DECORATE/actor classes'). It distinguishes from siblings like 'actor_state' and 'behavior_names' by its unique action of listing classes.

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?

No guidance is provided on when to use this tool versus alternatives like 'actor_state' or 'list_functions'. It does not include when-not-to-use, prerequisites, or explicit context for invocation.

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