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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds value by listing the full set of return fields (item name, descriptions, dates, bids, etc.), which is behavioral context beyond the annotations.

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 one sentence that front-loads the primary purpose, then enumerates return fields. It is efficient but the long list of fields could be condensed or omitted since it's a list; overall, it's clear and not verbose.

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?

With no output schema, the description compensates by listing 16+ return fields, providing significant detail. It covers input (sale_no, lot_no) and output comprehensively. Minor gap: no mention of behavior when the lot doesn't exist or error cases.

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 coverage is 100% and both parameters are documented. The description mentions 'identified by its sale number and lot number' but adds no semantic detail beyond what the schema already provides (name, type, description). Baseline score of 3 is appropriate.

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 explicitly states it returns 'full detail for a single GSA Auctions lot' and lists the specific fields returned. It clearly differentiates from siblings like gsa_search_auctions (search/filter) and gsa_auctions_closing_soon (time-limited list).

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 implies usage when you have a specific sale number and lot number, but provides no explicit guidance on when to use this tool versus siblings, no prerequisites (e.g., you need to first search for a sale), and no when-not-to-use conditions.

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