get_actor_properties

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Get all properties' implies a read operation, but it does not clarify what 'all properties' includes, how names are matched, whether the operation is purely local, or whether any side effects occur.

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 core statement is front-loaded and the example is minimal. The KB link is short but unexplained; overall it is concise without being overly terse.

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 simple one-parameter read tool with an output schema, it is nearly complete. The main gaps are lack of alternative-tool guidance and precise name-matching semantics, but the output schema covers return-value expectations.

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 schema lists only a string parameter named 'name' with no description, so the description adds the essential meaning that the value is an actor's name. The example provides invocation format, but exact-name semantics, case sensitivity, and matching behavior are left unspecified.

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 clear action and resource: 'Get all properties of an actor by name.' This distinguishes it from mutation tools like set_actor_property and spawn_actor, though it does not explicitly differentiate it from read-style siblings like get_actor_identity or spatial_describe_actor.

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 given on when to prefer this tool over alternatives such as get_actor_identity, find_actors_by_name, or get_actors_in_level. The KB reference and example show how to call it, but not when it should be chosen.

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