Look up the bilateral referral terms for a given partner brokerage. Returns buyer-side %, listing-side %, tail months, and any custom notes. Pass partner_id (UUID) OR partner_slug. Use this when scout.route_lead is about to fire and you need to confirm the split with the receiving brokerage.
| Name | Required | Description | Default |
|---|---|---|---|
| partner_id | No | UUID from partner_brokerages. | |
| partner_slug | No | Slug e.g. 'central-texas-realty-austin'. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden. It discloses that the tool is a read-only lookup and enumerates return values. While it doesn't detail error handling or idempotency, the transparency is adequate for a simple query 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 efficient sentences: first states purpose and outputs, second gives usage context and parameter guidance. Every sentence is necessary and front-loaded, with no redundant 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?
Given no output schema or annotations, the description covers core usage, expected returns, and invocation context. It lacks details on ambiguous input (e.g., if both parameters given) but is otherwise complete for a simple lookup 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 coverage is 100%, baseline 3. The description adds value by explaining the parameter options (partner_id vs. partner_slug) and their types (UUID, slug), clarifying usage beyond the schema descriptions.
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 the tool looks up bilateral referral terms for a partner brokerage, specifying exact return fields (buyer-side %, listing-side %, tail months, custom notes). It distinguishes itself from sibling tools by referencing scout.route_lead usage, making the purpose specific and unambiguous.
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 advises when to use ('when scout.route_lead is about to fire and you need to confirm the split') and how to call it (pass partner_id OR partner_slug). Lacks explicit 'when not to use' or alternative tools, but the guidance is clear and contextual.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a clearly distinct purpose, from agent profiles and comparisons to market data and lead management. Overlaps like find_agent vs find_public_agent are explicitly differentiated by live vs directory status.
All tools use snake_case and the 'scout.' prefix, but they mix verb_noun (e.g., compare_agents, search_listings) and noun_noun (e.g., agent_profile, coverage) patterns. However, the naming remains predictable and readable overall.
With 18 tools, the server covers agent discovery, brokerage info, market data, listings, lead management, referrals, and licensing—well-scoped for a real estate assistant without redundancy.
The tool set covers all key workflows: agent and brokerage search, market insights, school data, listing search, lead generation and purchase, referral management, and license verification, with no obvious gaps for its domain.
