ue_get_actor

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

The description discloses that the tool returns transform, class, and component list, indicating a read operation. However, it does not cover error behavior (e.g., missing actor) or any side effects. With no annotations, this is basic but not thorough.

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 13 words, with no filler. It is succinct and front-loaded, stating the purpose immediately.

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?

The description lists the three data items returned but does not specify the output format (e.g., JSON structure) or error handling. Given no output schema, more detail would be beneficial for a complete understanding.

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 description adds context that the 'label' parameter refers to the outliner label, which is helpful. However, schema description coverage is 0%, and the description does not explain expected format, case sensitivity, or how to retrieve the label. It adds some meaning but not enough to compensate.

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 specifies the verb 'Get' and the resource 'actor's transform, class, and component list', and identifies the lookup method 'by its outliner label'. This distinguishes it from siblings like 'list_actors' or 'set_actor_transform'.

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. There is no mention of prerequisites, typical use cases, 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.