listing__delete_assets

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the irreversibility statement is partly redundant. However, the description adds real value by disclosing that every id is validated against that app's library before deletion and that a single confirmation names each file — behavior an agent cannot infer from annotations.

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?

Four short sentences, front-loaded with the action and target, followed by prerequisites, safety behavior, and the destructive warning. No filler, and the most important constraint (irreversibility) lands last for emphasis.

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 two-parameter destructive tool with annotations and no output schema, the description covers action, prerequisites, validation, and irreversibility. Minor omissions such as the 50-id cap and what a successful/partial-failure response looks like are already handled by the schema, so the gap is small.

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%, so both parameters are already documented, including the accepted app identifier forms and the 1–50 item bounds on asset_ids. The description only adds that ids are checked against the target app's library, which is useful but marginal at this coverage level.

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?

States a specific verb and resource — deleting images/videos from an app's asset library — which cleanly separates it from siblings like listing__upload_asset and apps__asset_library__get. An agent can identify the operation and its target without opening the schema.

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?

Explains the required context ('Give the app and the ids of the files') and where ids must come from, so the agent knows how to prepare a call. It does not explicitly name an alternative tool or state when not to use it, so it falls short of full routing guidance.

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