ue5_get_object_property

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

With no annotations, the description carries the full burden. It does make the read-only nature and object-path requirement explicit, but it does not disclose behavior for invalid paths, missing properties, or how the value is returned. That leaves meaningful behavior unspecified.

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?

One sentence that front-loads the action and includes the two most important constraints (scope and path requirement) with no filler. Every word earns its place.

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 two-parameter getter with a complete input schema, the description plus parameter docs are largely sufficient. No output schema exists and the exact return representation is not specified, but the description's 'Read a property value' conveys the expected result well enough for a low-complexity tool.

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 100%, and both parameters already have clear descriptions, including a concrete object path example. The tool description adds no additional parameter semantics beyond re-emphasizing 'full' path, so the schema-driven baseline of 3 is appropriate.

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 names a specific action ('Read a property value'), a specific resource ('any UObject in the current level'), and the required addressing mechanism ('full Unreal object path'). This cleanly distinguishes it from the sibling ue5_set_object_property, making the intent immediately clear.

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 read-vs-write contrast with ue5_set_object_property makes the basic use case inferable, and the 'current level' scope provides context. However, the description does not explicitly state when to prefer this tool over siblings or mention any exclusions, so the guidance is implied rather than stated.

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