get_scene_info

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

No annotations are present, so the description bears full responsibility. It only lists what is returned but does not disclose any behavioral traits such as read-only nature, performance impact, or caching behavior.

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 front-load the key information: the purpose and the returned data. Every sentence provides value without unnecessary detail.

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 lists the main return fields (scene name, object list with hierarchy, counts, frame range, fps, render engine). It could mention any side effects or performance notes, but it is complete for a read-only info tool with no parameters.

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?

With 0 parameters, baseline is 4. The description adds meaning by detailing what the tool returns, which is necessary since the schema provides no parameter information.

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 full scene information including specific elements like object tree, hierarchy, frame range, fps, and render engine. It is distinct from sibling tools that focus on specific aspects (e.g., get_object_info for object details).

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?

The description implies this tool is for getting an overview of the scene, but it does not explicitly state when to use it over alternatives like get_object_info or get_node_tree. No exclusions or usage hints are provided.

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