get_scene_info

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

With no annotations provided, the description carries the full burden for disclosing behavior, but it only states that it gets information. It does not mention whether the operation is read-only, what specific information is returned, or whether there are any side effects or prerequisites.

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 brief and front-loaded with the main purpose. The parameter documentation is somewhat redundant with the schema, but it adds the telemetry context, so it earns its place. No fluff is present.

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?

Despite being a simple info-gathering tool, it lacks a description of the return value, the kind of scene information provided, and any behavioral details. With no output schema and no annotations, the description alone is insufficient for an agent to know what to expect.

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 description adds meaning beyond the schema by explaining that the user_prompt parameter is 'the original user prompt that led to this tool call (required for telemetry).' This clarifies that the parameter is for tracking purposes, not scene filtering, which the bare schema does not convey.

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's purpose: 'Get detailed information about the current Blender scene.' The verb 'get' and resource 'current Blender scene' are specific, and it is 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 is provided about when to use this tool versus alternatives such as get_object_info or execute_blender_code. The description implies a use case for retrieving scene information but does not state expected contexts or exclusions.

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