app_asset_library_videos_delete_instance

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses nothing. For a destructive DELETE operation, an agent needs to know whether the deletion is permanent, whether it requires elevated permissions, and what happens to associated placements — none of which is stated.

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 short, but it contains a pointless verbatim duplication — the route appears twice inside parentheses. Under-specification plus redundant text means the small amount of space is not used well.

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 destructive, unannotated mutation tool with no output schema, the description should at minimum state irreversibility and permission requirements. It provides none of this, leaving the agent with only a URL template to work from.

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 100% and the single parameter is documented in the schema as 'the id of the requested resource', so the schema does the heavy lifting. The description adds no syntax, format, or ID-source detail beyond what the schema already provides, making the baseline 3 appropriate.

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 restates the HTTP route 'DELETE /v1/appAssetLibraryVideos/{id}', which conveys a specific verb (delete) and resource (app asset library video), so an agent can infer the intent. However, it is essentially a raw route dump that duplicates the tool name rather than describing the operation in plain language, and it does nothing to distinguish itself from siblings like app_asset_library_videos_get_instance or app_asset_library_videos_update_instance.

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?

There is no guidance on when to use this tool versus alternatives such as app_asset_library_videos_update_instance or app_asset_library_videos_create_instance. No preconditions, no exclusions, no context about what resource state is required before deletion.

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