create_empty

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

Annotations already declare destructiveHint=true, so the safety profile is known. The description adds context that the Empty is a reference/control point, which is useful, but it does not disclose any additional behavioral traits such as scene modifications or reversibility. With annotations covering the safety aspect, this is adequate.

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 without fluff, efficiently stating the core purpose. It is well-structured and front-loaded, though it omits parameter details which are not required for conciseness alone.

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?

The tool is simple with three optional parameters, and an output schema exists. However, the description provides no explanation of the parameters, their allowed values, or usage context, making it incomplete for an agent to select appropriate arguments. It fails to compensate for the 0% schema description coverage.

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 0%, so the description must compensate by explaining parameters, but it does not mention any of the three parameters (name, location, display_type) at all. This fails to provide necessary meaning beyond the schema, making parameter understanding impossible from the description.

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 'Buat objek Empty (titik referensi/kontrol)', which translates to 'Create an Empty object (reference/control point)'. It uses a specific verb and resource, and distinguishes this tool from generic creation tools like 'create_object' by specifying the Empty object type.

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 such as create_object or other specific creation tools. There are no mentions of use cases, exclusions, or conditions.

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