vast_update_non_linear_media

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'Update', which is a write operation, but doesn't state whether it's a partial or full update, any permission requirements, reversibility, effects on related entities, or what the response will look like. This is a significant gap for a mutation tool.

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, concise sentence that is well-structured and front-loaded with the verb and resource. It doesn't waste words, though it could be slightly more informative while still remaining concise.

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?

For a mutation tool with 5 parameters, no output schema, and no annotations, the description is skeletal. It fails to explain update semantics (partial/full), return values, prerequisites, or error scenarios, leaving the agent without enough context to invoke it confidently.

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 descriptions cover all parameters (100% coverage) with clear definitions for id, name, width, height, and mime_type. The description itself adds no parameter-specific semantics, so the baseline of 3 is appropriate because the schema already does the heavy lifting.

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 action (update) and the resource (VAST non-linear media), which distinguishes it from sibling tools like create, get, or delete. However, it doesn't provide any additional context about what 'non-linear media' means or what the update entails.

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 word 'existing' implies this tool is for updating records that already exist, which gives a hint about when to use it. However, there is no explicit guidance on when to use this versus alternatives like vast_create_non_linear_media or vast_get_non_linear_media, and no exclusions are mentioned.

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