make_single_user

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

No annotations are present, so the description carries full burden for behavioral disclosure. It indicates a mutation operation but does not disclose side effects (e.g., effects on other objects sharing the datablock), reversibility, or permission requirements. The description is insufficient for safe usage.

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 and well-structured. It provides a one-line purpose followed by a clear Args section with each parameter explained. No redundant information; every sentence is necessary. The format is front-loaded with the core operation.

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 that the tool operates on shared datablocks (a potentially impactful operation), the description lacks important contextual details such as reversibility, warnings about data loss, or behavior when both parameters are false. Although an output schema is mentioned (confirmation dict), no structure is provided. The description is insufficient for a tool with no annotations.

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?

With schema description coverage at 0%, the description compensates by explaining each parameter's role: 'object' controls making the object single-user, 'data' controls the object's data (e.g., mesh). This adds meaning beyond the schema's type-only definitions. However, the descriptions are brief and could elaborate on the effects of setting each to false.

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 purpose: 'Make an object's data single-user (unlink shared datablocks).' It uses a specific verb ('make') and resource ('object's data single-user'), distinguishing it from sibling tools like duplication or property setting. The term 'single-user' is a specific Blender concept.

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 does not provide any guidance on when to use this tool versus alternatives. It lacks context about scenarios where unlinking shared datablocks is appropriate or necessary. No exclusions or prerequisites are mentioned.

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