restore_assets

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

Discloses the side effect of moving assets out of trash. However, no annotations are present, so the description carries the full transparency burden. Could mention error handling or permissions, but the side effect is a key behavioral detail.

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?

Three concise sentences plus structured Args/Returns. Front-loaded with main purpose, no wasted words. The important guidance about selective recovery is placed early.

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?

Covers the essential information: what it does, when to use, side effect, parameter, and return value. Could be improved by mentioning validation or whether the operation is idempotent, but it's sufficient for safe usage.

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 description explains that 'asset_ids' is a list of asset UUIDs currently in trash, which adds context beyond the schema's type definition (array of strings). With 0% schema description coverage, the tool description effectively documents the parameter.

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?

Clearly states the verb 'restore', resource 'assets from trash', and destination 'active library'. Distinguishes from sibling 'restore_trash' by specifying selective recovery vs mass restore.

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?

Explicitly tells when to use this tool (selective recovery) and when not to use it (use restore_trash for everything at once), directly naming the alternative.

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