sales.history

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

With no annotations, the description fully handles behavioral disclosure. It notes the side effect of include_liens=true making an extra API call and highlights that 13 states do not disclose sale prices. It does not explicitly state the tool is read-only, but the context implies it. No contradictions.

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?

Concise yet informative; the purpose is front-loaded, followed by usage guidelines, behavioral notes, and parameter clarification. Every sentence adds value with no redundancy.

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?

Despite no output schema, the description explains return event fields (date, price, buyer, seller, deed type) and flags for undisclosed prices. It also covers state-level limitations and side effects, making it complete for this tool's complexity.

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%, so the description adds value beyond schema by clarifying that 'since' is a client-side filter and that 'include_liens' adds an extra API call with default false. This nuance aids correct usage.

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 provides a deed/transaction timeline for a parcel, listing specific event details (date, price, buyer, seller, deed type). This specific verb+resource distinguishes it from sibling tools like parcel.search or valuation.estimate.

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 when to use (user asks about transaction history, flip activity, holding period) and when not to use (market-wide sold properties or current value estimation), with direct references to alternative tools (parcel.search, valuation.estimate).

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