daz_get_scene_layout

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 implies a read-only query through the verb 'Get' and the nature of the output, but it does not explicitly state that the tool is non-destructive or safe, nor does it mention any side effects or permissions needed.

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 with a one-line summary, a contextual paragraph, and clearly labeled Args, Returns, and Example sections. Every sentence adds value, and there is no redundancy or 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?

Given the tool's moderate complexity and the presence of an output schema, the description covers the purpose, parameter, return structure, and an example. It lacks only error handling or performance notes, but for a simple query tool, it is sufficiently 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 schema coverage is 0%, meaning the schema provides no description for parameters. The description compensates fully with an Args section listing valid values ('figures', 'cameras', 'lights', 'props') and explaining the default behavior, adding significant meaning beyond the raw schema.

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 'Get a spatial map of all scene nodes with positions and bounding boxes.' It uses a specific verb and resource, and the mention of 'bird's-eye view' distinguishes it from siblings like daz_get_node or daz_get_world_position, which focus on individual nodes.

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 provides context ('useful for reasoning about character spacing, prop placement, and camera coverage') but does not explicitly indicate when to use this tool versus alternatives like daz_get_node or daz_get_bounding_box. No 'when not to use' guidance is provided.

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