get_scene_properties

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

No annotations are provided, so the description carries the full disclosure burden. It usefully reveals sentinel value (-1.0 for tempo), Live version conditional fields, and a full inventory of returned data. It doesn't explicitly state that the operation is read-only, but the verb 'Get' strongly implies no side effects.

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 concise and front-loaded. The first sentence gives the purpose, followed by a compact list of returned fields and a single argument explanation. Every sentence contributes meaningful information.

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 read-only getter with one parameter, the description covers the core needs: it names the resource, explains the parameter format, and enumerates returned properties. It doesn't discuss error behavior for invalid indices, but an output schema exists and the behavior is predictable for such a 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?

The schema only provides a type and title for scene_index, with 0% description coverage. The description adds the crucial clarification that it is a zero-based index, which is essential for correct usage and not derivable from the schema alone.

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 states 'Get properties of a specific scene' and lists the exact properties returned. It lacks explicit differentiation from sibling get_scene_info, but the detailed property list makes the specific resource unambiguous.

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?

It implies use when retrieving scene properties, but provides no explicit when-to-use guidance or alternatives. There are no exclusions or comparisons to other scene-related getter tools.

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