studio_set_properties

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

Description implies mutation but does not disclose behavioral details such as whether properties are replaced or merged, required permissions, error handling, or side effects. With no annotations, the description carries the full transparency burden and falls short.

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 a single sentence, which is concise but lacks structure. It could be expanded to front-load key details without becoming verbose.

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 has 2 required parameters (one an object), no output schema, and no annotations, the description is critically incomplete. It omits essential context like whether properties are merged or replaced, validation rules, and success/failure behavior.

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 description coverage is 0%, and the description adds no meaning to the parameters 'instancePath' or 'properties'. No examples, constraints, or format hints are provided 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 action ('Set') and the resource ('validated serialized properties on one Instance'), distinguishing it from siblings like studio_get_properties. However, the phrase 'validated serialized' is jargon that could benefit from elaboration.

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?

No guidance is provided on when to use this tool versus alternatives like studio_patch_instances or studio_set_camera. The description lacks explicit when-to-use or when-not-to-use context.

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