get_scene_info

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

Annotations indicate readOnlyHint=true and destructiveHint=false. The description adds context about query-triggered object lists and the summary contents. No contradictions; it appropriately extends the annotation-implicit behaviors.

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 two sentences, adequately front-loaded with the core purpose, and then adds query details. No extraneous content.

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?

While the summary and query behavior are described, the other parameters (name, global_id, ifc_class) are mentioned in the schema but not explained. Since there is no output schema, the description should cover these aspects for full clarity. It is partially 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?

Schema coverage is low (25%: only query has a description). The description explains the query parameter and its supported values, but does not explain name, global_id, or ifc_class parameters. With low coverage, the description should compensate but fails to do so.

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 returns a summary of the current Blender scene with specific elements (scene name, object count, selection, collections, IFC availability) and further explains query-based filtering. It distinguishes from siblings like get_selected_objects (which focuses on selection) and get_ifc_project_info (IFC-specific).

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 guides on when to omit query (scene summary only) and lists supported queries. However, it does not explicitly guide on when to use this tool versus siblings like get_selected_objects or execute_blender_code for object queries.

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