list_deleted_file_sets

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

No annotations are provided, so the description carries the full burden. It states 'List' which implies a read-only operation, but it does not disclose what the delete queue represents, whether results are paginated or ordered, whether any authentication or permissions are needed, or what the response contains. The phrase 'delete queue' is ambiguous.

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 with no redundant words. 'List file sets in the delete queue' is front-loaded and every word contributes to the meaning.

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 zero-parameter list tool, the description is minimally adequate, but it leaves gaps: the meaning of 'delete queue' is not explained, and there is no output schema to clarify the return structure. It is not as incomplete as a mutation tool, but it could still benefit from clarifying what 'delete queue' means and what is returned.

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 tool has zero parameters and the schema is empty, so there is no parameter semantics burden for the description. Baseline for zero parameters is 4; the description does not need to add parameter details.

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 specifies a clear action ('List'), a resource ('file sets'), and a scope ('in the delete queue'). It is not a tautology and is distinguishable from sibling tools like list_asset_file_sets and list_deleted_formats, though it does not explicitly name those alternatives.

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?

The description provides no guidance on when to use this tool versus list_asset_file_sets, list_file_set_files, or list_deleted_formats. There is no mention of prerequisites, intended use cases, or exclusions, so the agent must infer usage from the tool name alone.

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