alt_auctions

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

With no annotations provided, the description carries the full burden—and it delivers: it discloses credential-free public data, server-side search-key scoping, live/currently-live behavior, and explicit exclusions. This gives an agent a clear behavioral model without relying on structured metadata.

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?

Front-loaded with the core purpose and efficiently structured, but somewhat redundant: 'Search Alt's own live 24/7 auctions' and 'Searches Alt's own currently live auctions' repeat the same point, and the scoping claim is restated multiple times in slightly different forms.

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?

Complete enough for an agent to select and invoke the tool correctly: scope, exclusions, data source, and parameter-value guidance are all covered. Since there is no output schema, some information about the response shape or pagination behavior would add completeness, but it is not critical for a credential-free read-style search tool.

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%, so the baseline is 3: the schema already documents all six parameters. The description adds little beyond pointing to alt-categories for accepted category/grading_company/sort values, which is helpful but not substantial additional semantics.

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: 'Search Alt's own live 24/7 auctions.' It further defines scope by referencing the exact pool (alt.xyz/browse 'Auctions' tab filtered to Alt source) and explicitly contrasts itself with alt-search, making differentiation from siblings clear.

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?

Provides clear context by naming alt-search as the alternative and explaining what this tool never returns (other auction house listings, Alt fixed-price items). It does not, however, explicitly state 'use alt-search instead when you need those results' or address other related sibling tools like alt_asset, alt_sold_listings, or alt_listing, so the guidance is strong but not fully exhaustive.

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