find_unused_assets

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

No annotations, but description details return behavior: returns first `limit` unused assets and a `truncated` flag, and explains scan halting logic. Missing explicit read-only statement but clearly non-destructive.

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: purpose, composition+use case, return behavior. No wasted words.

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 main behavior and output structure (unused assets + truncated flag) despite no output schema. Could clarify exact output format but acceptable given tool simplicity.

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?

All parameters have schema descriptions (100% coverage). Description adds significant value: default '/Game', recursive hint for path_under; default 100, max 10000, and scan halting behavior for limit.

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 it enumerates assets and reports those with zero referencers, distinguishing it from siblings like find_assets and inspect_asset via composition hint.

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 states 'Useful for content cleanup audits before shipping.' Does not detail when not to use, but context implies alternatives for simple listing or inspection.

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