List historical deletions

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

Annotations already cover readOnly/idempotent/openWorld, but the description adds real value beyond them: 'rows are frozen at last sighting' discloses snapshot semantics and 'Cost: 5 credits flat' discloses billing impact. It stops short of describing pagination mechanics or return fields.

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?

Two sentences, zero filler, with the core scope front-loaded and the cost note placed last where it belongs. Every clause carries information.

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?

No output schema exists, but the description supplies the essential semantics (snapshot rows, 24-month window, paging, flat cost) and the read-only annotations cover safety. It could say more about what a row contains, which is the main residual gap.

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 each parameter (sort, limit, offset, since_month, min_peak_downloads) is already documented in the schema. The description adds no parameter-level meaning beyond what the schema provides, so the baseline 3 applies.

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 ('Paged list of models deleted from Hugging Face'), plus a scope (last 24 months) and the underlying endpoint. It does not distinguish itself from near-neighbors like list_delisted or get_deletions_summary, so an agent can't tell them apart without opening both schemas.

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 versus get_deletions_summary (a summary) or list_delisted (a different lifecycle state). The 24-month window is the only implicit scoping cue; no exclusions or alternatives are named.

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