update_model_instance

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

With no annotations provided, the description must disclose behavior, but it only states 'update', implying mutation without explaining side effects, scope of metadata changes, or whether existing metadata is overwritten. No information is given about required permissions, failure modes, or what happens if the folder is invalid.

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 short sentence with no filler or redundant information. It is easy to parse, though it sacrifices needed detail for brevity.

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?

This is a simple mutation tool with one parameter, but the description leaves essential context unclear: what exactly is read from the folder, how the folder path should be provided, and whether this operation is destructive or additive. The lack of annotations or output schema makes this gap more significant.

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 schema has one parameter, 'folder', with an empty description and 0% schema coverage. The description mentions 'from folder' but does not clarify what kind of folder, what path format is expected, or how the folder relates to the model instance metadata. This is insufficient compensation for the missing schema documentation.

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 states a specific verb and resource: 'Update model instance metadata', which distinguishes it from siblings like update_model and update_dataset. The phrase 'from folder' adds some context, though it is not fully explained.

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 such as update_model or create_model_instance. There is no mention of prerequisites, intended workflows, or situations where a sibling tool would be more appropriate.

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