blender_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 of behavioral disclosure. It communicates the read-only nature through 'Summarize', scopes the operation to the open file, and reveals a concrete limit ('up to 200 objects'). It does not describe failure behavior when no file is open, but the core behavior is transparent enough.

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, front-loaded sentence with zero filler. It efficiently communicates the verb, target resource, scope, and a relevant limit in a compact form.

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?

For a zero-parameter tool with no output schema, the description is substantially complete: it states what information is summarized and the object cap. Minor details such as exact return structure or error behavior are not specified, but this is acceptable for a simple inspection 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?

This tool has zero parameters and the schema has no properties, so there are no parameter semantics for the description to compensate for. The baseline of 4 applies because there is nothing missing on the parameter side.

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 action ('Summarize'), the specific resource ('the open Blender file'), and exactly what it covers (scene, mode, collections, and up to 200 objects). This is specific enough to distinguish it from siblings like blender_exec or blender_viewport, even without naming them.

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 when the tool should be used: when a summary of the current Blender scene/collections is needed. However, it does not explicitly state when to use this tool instead of siblings like blender_health or blender_viewport, nor does it mention any exclusions.

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