get_scene_info

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

No annotations are present, so the description carries the full burden. It discloses that the return includes blender_version and blender_version_string, which is useful behavioral detail. However, it does not enumerate the full scope of 'detailed information' or mention potential errors or side effects, leaving some opacity.

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 well-structured: a clear one-line purpose, a specific detail about version fields, and a parameter list. Every sentence earns its place with no redundancy.

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?

Given the tool's low complexity (single optional parameter, no output schema), the description mentions the key version fields and purpose. However, 'detailed information' remains vague, and without an output schema the agent lacks a complete picture of available scene data, which could matter for downstream decisions.

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 has 0% description coverage, but the tool description explains that user_prompt is an optional original user prompt used for telemetry. This adds semantic meaning beyond the schema's type/default, effectively compensating for the lack of schema descriptions.

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 ('Get') and resource ('detailed information about the current Blender scene'), which clearly distinguishes it from sibling tools like get_object_info and get_viewport_screenshot. It further specifies that it includes blender_version and blender_version_string, adding concrete scope.

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 explicit when-to-use or alternative guidance. The mention of 'for API branching' implies a usage context, but it does not state when to prefer this over get_object_info or other tools. This is implied usage only, not explicit direction.

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