get_scene_property

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

The readOnlyHint annotation already declares this as a safe read operation, and the description simply repeats 'read' without adding behavioral context. It does not disclose what happens if the property is missing, whether all properties are accessible, or the return format. Given the annotation, the low bar is not met with extra value.

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 short sentence, which is concise in length but severely under-specified. It omits essential information about the parameter and behavior, making it under-specification rather than effective conciseness.

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 tool with one unknown parameter and no detailed schema, the description is incomplete. While an output schema exists (not shown), the input semantics are undocumented, and with many sibling tools offering similar functionality, the context is insufficient for correct invocation.

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%, so the description carries the full burden for explaining the 'prop' parameter. It merely says 'scene property' but does not provide any valid values, examples, or format. This is insufficient for a required 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 uses a specific verb 'Baca' (read) and identifies the resource as 'scene property', making it clear this is a read operation on scene properties. However, it does not differentiate from sibling tools like get_scene_info, which likely also retrieves scene data, so it lacks sibling differentiation.

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?

There is no guidance on when to use this tool versus alternatives. With many sibling tools such as get_scene_info and scene_summary, the description does not mention any exclusions or preferred contexts, leaving the agent without usage direction.

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