get_scene_info

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

No annotations; description only states it gets scene info. Does not disclose side effects, read-only nature, or other behavioral traits beyond the basic purpose. The parameter note about telemetry is minimal.

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?

Two sentences: clear purpose and parameter explanation. No redundant information. Efficient but could be slightly more concise about parameter.

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?

No output schema or annotations; description does not specify what information is returned (e.g., objects, materials, camera). Missing prerequisites like scene existence. Incomplete for a getter 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?

Schema coverage is 0%, but description explains user_prompt is 'the original user prompt that led to this tool call (required for telemetry)'. Adds meaning beyond the schema's 'User Prompt' title.

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?

Clear verb ('get') and resource ('detailed information about the current Blender scene'). Distinct from sibling tools like get_object_info or get_viewport_screenshot.

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?

No guidance on when to use vs alternatives or prerequisites. Only describes what it does, not context of use.

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