daz_batch_set_properties

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

Description discloses individual error handling for each operation, that failed operations do not abort the batch, and that operations execute in a single script call. As there are no annotations, it bears full burden and does so adequately, though it could mention whether operations are atomic or if partial effects are committed.

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-organized with sections for purpose, args, returns, examples, and a note. Every sentence adds value, examples are clear, and the structure is easy to parse. No redundant information.

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 lack of annotations and presence of an output schema, the description provides complete context: purpose, argument semantics, return structure, usage guidance, and examples. It addresses the tool's complexity (batch operations with error handling) comprehensively.

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 description adds substantial meaning beyond the input schema, which only defines 'operations' as an array of objects. It specifies each operation object contains nodeLabel, propertyName, and value, with types and descriptions, compensating for the schema's additionalProperties: true and lack of detail.

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?

Description clearly states the tool sets multiple properties on one or more nodes in a single call. It distinguishes itself from the sibling daz_set_property by emphasizing batch efficiency. The verb 'Set' and resource 'multiple properties on nodes' are precise.

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?

Explicit note states this tool is more efficient than calling daz_set_property individually, guiding the agent to use it for batch operations. However, it does not explicitly list scenarios where it is not appropriate or alternative tools beyond daz_set_property.

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