daz_get_world_position

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

No annotations are present, but the description transparently lists the returned data (position, rotation, scale) and input (node_label), implying it is a read-only query without side effects.

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 concise (two sentences plus a clear Args and Returns block), front-loaded with the purpose, and every part adds value without redundancy.

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 simplicity (one parameter, no nested objects), the description fully explains input and output, including an example of the return structure, making it complete for the tool's scope.

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 only defines 'node_label' as a string with no description, but the tool description adds explicit meaning: 'Display label of the node (e.g. "Genesis 9", "Camera 1")', compensating for 0% 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 verb 'Get' and the resource 'world-space position, local position, rotation, and scale of a node', distinguishing it from sibling tools that modify or apply transformations.

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 mentions it is 'useful before making relative positioning decisions', which provides context, but does not give explicit when-not-to-use or alternatives among sibling tools.

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