blender_scene_summary

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

The description discloses what the tool reports (object counts, armatures, meshes, actions, save state) but does not explicitly state that it is read-only or safe, and there are no annotations to cover this. The term 'summarize' implies non-mutating behavior, but side effects and operational details are not addressed.

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, concise sentence that front-loads the verb and resource, then lists the key summary points efficiently. Every word adds value and there is no filler.

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?

With no parameters and no output schema, the description sufficiently covers what the tool does and what information it provides. It could benefit from mentioning typical use cases or a note about the return format, but for a simple summary tool, the information is largely complete.

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, which earns a baseline of 4 per the rubric. The description adds no parameter-level detail, but none is needed since there are no parameters to explain.

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 summarizes the open Blender file and lists specific aspects (object counts, armatures, meshes, actions, save state), making its function evident. However, it does not explicitly distinguish itself from sibling tools like blender_status or blender_list_objects, though the summary nature is implied.

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 on when to use this tool versus alternatives. It does not mention that it should be used for a high-level overview before detailed operations, nor does it contrast with blender_status or blender_list_objects. Agents are left to infer appropriate contexts.

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