rna-set_property

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

With no annotations, the description carries the full burden of disclosing side effects, validation, or safety concerns. It only mentions that the value is JSON-encoded, but does not explain potential risks like setting invalid data, undo behavior, or whether changes are permanent.

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, front-loaded sentence with no wasted words. It is appropriately concise for its core purpose, though some behavioral details are missing.

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, output schema, and sparse parameter info, the description is insufficient. It does not explain return values, potential failures, or how the JSON encoding should be formatted beyond a generic mention. This could be dangerous for an arbitrary property setter.

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 has 0% description coverage (only titles), so the description must compensate. It mentions 'path under bpy.data' and 'value is JSON-encoded', which overlaps with the schema titles but adds little beyond them. No additional examples, format details, or constraints are provided.

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 'Set' and the resource 'a data property by path under bpy.data', which identifies its function and distinguishes it from generic property setters like properties-set. However, it does not explicitly differentiate from sibling tools like rna-call_operator or properties-set.

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. The description only states what it does, leaving the agent to infer use cases from the bpy.data path mention. There are no exclusions or when-not-to-use instructions.

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