create_model_instance

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

There are no annotations, so the description carries the full burden of behavioral disclosure. Saying 'Create' implies mutation, but it does not describe side effects: what gets uploaded, whether the instance is versioned, whether existing data is overwritten, or what success/failure looks like.

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 five words with no filler or redundancy. It is front-loaded and easy to parse, though it is so terse that it leaves important behavioral and usage gaps.

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 no annotations, no output schema, zero documentation on the only parameter, and several closely related model-instance tools, the description is too sparse for an agent to invoke it confidently and correctly.

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 only parameter, 'folder', has an empty schema description and 0% coverage, so 'from folder' is the sole hint. It adds the idea that this parameter is the source folder, but it does not clarify expected path format, local versus remote paths, or how the folder relates to the model instance.

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 names the action ('Create') and the resource ('model instance'), and indicates the source ('from folder'). This is specific enough to distinguish from list/update/delete operations, but it does not differentiate from closely related siblings such as init_model_instance or create_model_version.

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 about when to use this tool versus alternatives like init_model_instance, update_model_instance, or create_model_version. It also omits prerequisites, such as whether an existing model must already exist before creating an instance.

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