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

No annotations provided, so description carries burden. Discloses key traits: free to call, returns redacted previews, limited to SC+GA, and lists signal types. Does not mention rate limits or auth, but acceptable for a search tool.

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 concise sentences front-loading purpose, return type, cost, and geographic scope. No wasted words; every sentence adds value.

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?

Covers major aspects: what, where, cost, relation to sibling tool. Lacks return format or pagination details, but acceptable given no output schema and 8 parameters. Slightly incomplete for a tool this complex.

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 baseline is 3. Description lists signal types but adds no semantic depth beyond schema parameter descriptions. Adequate but not exceptional.

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 previews seller-signal leads (probate, NOD, FSBO, expired, tax-delinquent) for sale through the Scout marketplace. It distinguishes from scout.purchase_lead by noting full data requires purchase, and contrasts with sibling tools like scout.get_seller_signals.

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 geographic limitation ('SC + GA only') and that calling is free. Mentions when to use purchase_lead for full details. No explicit when-not-to-use or alternatives list, but context is clear for common scenarios.

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