set_attribute

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

No annotations are provided, so the description carries the full burden for behavioral disclosure. It does not mention side effects like whether the attribute is created if absent, whether existing values are overwritten, error conditions (e.g., nonexistent instance), or any permission requirements. The only behavioral detail is the list of supported types, which is more of a parameter constraint than a disclosure of 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 two sentences long, front-loaded with the action and object, and the second sentence concisely enumerates supported types. No redundant or filler content exists; every word contributes to understanding the tool's purpose and constraints.

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?

For a mutation tool with no annotations and no output schema, the description is adequate but lacks depth. It explains what the tool does and lists accepted types, but does not cover critical context such as error handling, behavior when attributes already exist or are created, or any prerequisites for the instance path. Given the tool's moderate complexity and schema richness, more behavioral context would be needed for full completeness.

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?

Schema description coverage is 100%, providing detailed descriptions for all parameters including structural examples for Vector3, Color3, and UDim2. The description adds explicit support for primitive types (string, number, boolean) that are not listed in the schema's valueType hint, clarifying that these can be used without a type hint. This adds semantic value beyond the 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's function with a specific verb and resource: 'Set an attribute value on a Roblox instance.' This distinguishes it from siblings like set_property, get_attribute, and delete_attribute, which operate on different resources or actions. The supported types add useful scope without ambiguity.

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 implies usage by naming the operation, but it does not explicitly state when to use this tool versus alternatives like set_property or handle attribute-specific edge cases. No when-not-to-use or alternative tool references are provided, so the agent must infer from the tool name and sibling context.

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