Assets Update

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

With annotations indicating readOnlyHint=false and destructiveHint=false, the description adds no new behavioral context. It does not mention permissions, side effects, error conditions, or return values, leaving the agent without useful information beyond the raw annotation hints.

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, front-loaded with the action verb 'Update'. It wastes no words, though its brevity contributes to the lack of important details.

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?

Given the input schema has 8 parameters, very low schema coverage, and no output schema, the description is woefully incomplete. It does not explain that other fields are updatable, what the response looks like, or any additional context needed for an agent to confidently invoke the tool.

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 only 13% (only 'id' has a description), so the description must compensate for the other parameters. It mentions only 'name' and 'visibility', leaving six parameters (size, width, format, height, durationSeconds) undocumented and unexplained, failing to provide semantic meaning for the full parameter set.

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 tool updates an asset by id, distinguishing it from sibling create/delete/get tools. However, it says only 'name or visibility' can be updated, while the schema includes size, width, format, height, and durationSeconds, so it understates the tool's full capabilities.

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 on when to use this tool versus alternatives like assets_create or assets_delete. The description simply states the function without context on prerequisites, exclusions, or situations where another 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.