get_scene_capture_2d_properties

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

Annotations already declare readOnly, non-destructive, and idempotent, so the safety bar is covered. The description adds value beyond that by clarifying it triggers no Modify, no capture, and no save, which is behavioral context the readOnly hint alone doesn't fully convey.

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?

Front-loaded with the core action and property list, then the reader constraint, then the return shape. Dense but largely earned; the inline '(base)' qualifiers are slightly noisy but the return-value block is justified given no output schema.

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?

With no output schema, the description fully supplies the return shape (nine named fields with types) plus the read-only constraint, so an agent has everything needed to call and interpret the result correctly.

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% with a single documented actor_name parameter, so the schema carries the semantics. The description adds no format or identification detail beyond what the schema provides; baseline 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?

States a specific verb (read back) and resource (every data property of a SceneCapture2D actor's USceneCaptureComponent2D), then enumerates exactly which properties are returned. It also names the sibling set_scene_capture_2d_properties as its round-trip counterpart, so an agent can distinguish the two without opening a schema.

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?

Explicitly bounds usage with 'Pure reader — no Modify, no capture, no save' and points at the counterpart setter for the write path. It does not spell out a when-to-use condition beyond the read/write split, but the round-trip reference gives a clear alternative.

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