get_scene_info

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

The readOnlyHint annotation already indicates a safe read operation, and the description reinforces this with 'Get.' The description adds value by specifying the metadata fields, but it does not disclose any additional behavioral nuances such as performance implications or whether the scene must be loaded.

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 sentence that enumerates the returned fields efficiently without redundant wording. Every phrase 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?

The description is sufficient given the tool has no parameters and an output schema is available to detail the return structure. The listed fields cover the essential scene metadata categories, and nothing appears missing.

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 tool has zero parameters and the input schema is empty, so schema coverage is complete. With no parameters to explain, the description does not need to add semantic details, earning the baseline score of 4.

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 the tool retrieves current scene metadata and enumerates specific fields (name, frame range, FPS, render engine, object/material counts). This distinguishes it from sibling tools like get_object_info or get_render_settings.

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?

Usage is implied through the phrase 'current scene metadata,' suggesting it is for scene-wide info rather than object-specific or render-specific details. However, there is no explicit guidance on when to prefer this tool over alternatives such as get_object_info or get_render_settings.

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