Get Blender Scene Info

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

Annotations already provide readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=false. The description adds valuable context beyond this: it specifies the scope ('complete scene metadata including all objects'), output formats, and behavioral details about what data is returned (objects, materials, collections, world). No contradiction with annotations.

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 well-structured and front-loaded with the core purpose. Each section (purpose, args, returns, usage guidelines) is concise and earns its place with no redundant information. The text efficiently communicates essential information without unnecessary elaboration.

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?

Given the tool's complexity (scene-wide query), rich annotations, and lack of output schema, the description provides complete context. It explains what data is returned, output formats, and usage boundaries. The annotations cover safety aspects, and the description fills in behavioral details, making it fully adequate for an agent to use the tool correctly.

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 description coverage is 100%, with the parameter 'response_format' fully documented in the schema. The description adds minimal value beyond the schema by briefly mentioning the parameter in the 'Args' section and describing output formats, but doesn't provide additional semantic context. Baseline 3 is appropriate given high schema coverage.

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 with specific verbs ('Query', 'Returns') and resources ('Blender scene hierarchy, objects list, materials, and world settings'). It distinguishes from sibling tools like blender_get_object_info (single object) by emphasizing 'complete scene metadata' and 'all objects'.

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 explicitly provides usage guidance with 'Use when:' and 'Don't use when:' sections. It names specific scenarios ('understand current scene state, find object names, verify scene setup') and directs to alternatives ('use create/modify tools instead'), clearly differentiating from sibling modification tools.

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