geometry-create_metaball

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It says only 'create', implying a state change, but gives no details about side effects, return values, whether a new object is added to the scene, or how parameters affect the outcome. This lacks any behavior beyond the initial verb.

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, extremely terse sentence with zero wasted words. It is immediately parsed and front-loaded with the primary verb and object, making it easily scannable for an agent.

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?

With 6 parameters, no annotations, and no output schema, this description is highly under-specified. The agent cannot know what exactly happens when the tool is called, what the return value is, or how parameters affect the primitive. A creation tool should at least indicate that it adds a new of scene object, but that is left implicit.

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% and the description 'Create a metaball primitive' adds nothing about the meaning of the 6 parameters. The parameter titles in the schema are self-explanatory, but the description does not help the agent understand how to use or relate parameters, failing to compensate for no description coverage.

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 'Create a metaball primitive' clearly states the specific action (create) and resource (metaball primitive), which distinguishes it from sibling geometry creation tools like create_curve, create_surface, or create_grease_pencil. It is a succinct, unambiguous statement of purpose.

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 gives no guidance on when to use this tool versus alternatives, and no explicit context or exclusions. It only states what the tool does, leaving the agent to infer usage from the name alone. No sibling comparisons or prerequisite conditions are mentioned.

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