vast42_update_linear

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, but it only states 'Update' without explaining whether it performs a partial patch or full replacement, what fields are affected, or what the response contains. No side effects, auth requirements, or idempotency are mentioned.

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 redundant words, making it highly concise. However, it is arguably too sparse to provide meaningful guidance, but for pure conciseness it earns a 4 rather than a 5 because it lacks critical context.

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 tool with 5 parameters and no output schema or annotations, the description is incomplete. It does not clarify whether the update is partial or complete, what happens if required fields are omitted, or what the return format is. Sibling CRUD tools exist, but without additional context, the description is insufficient for reliable invocation.

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 coverage is 100% as every parameter has a clear description. The description adds no extra parameter-level context beyond the schema, which already defines id, name, bitrate, duration, and mime_type. This meets the baseline for high schema 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 clearly states the verb 'Update' and the specific resource 'VAST 4.2 linear media', distinguishing it from create/delete siblings. The version qualifier differentiates it from the similar 'vast_update_linear_media' tool. No ambiguity.

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 provides no guidance on when to use this tool versus alternatives like vast42_create_linear or vast42_delete_linear. It does not mention that an existing ID is required or that this is for modifying an existing entity, leaving usage entirely implied by the name.

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