qobrix_get_leads_by_property

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

With no annotations provided, the description carries the full burden. It discloses that the tool returns paginated results, identifies the matching pattern, and clarifies the propertyId requirement. However, it does not explicitly state read-only behavior or performance trade-offs (e.g., fast path vs. boost), which are left to the schema.

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 somewhat long (7 sentences) but each sentence provides distinct value—purpose, business question, domain pattern, usage timing, alternatives, parameter clarification, and pagination. Minor redundancy exists between the first and third sentences, but overall it is well-structured and front-loaded.

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?

Without an output schema, the description appropriately confirms that the tool returns matching leads and notes pagination. The schema covers page/limit mechanics thoroughly, and the domain context makes the meaning of 'matching' clear enough. It could be even more complete by specifying what fields each lead includes, but this is a minor gap.

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?

The schema already provides 100% coverage with detailed descriptions for all three parameters, including page/limit behavior with boost. The description's mention that 'propertyId is the Property UUID' largely duplicates the schema's 'Property UUID to find matching leads for' and does not add meaningful new 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?

The description uses a specific verb-object structure with a clear resource: 'Get matching leads for a property.' It also explicitly differentiates from siblings by naming itself the 'supply-side matching' tool and referencing complementary tools like qobrix_get_lead_properties and qobrix_search_opportunities.

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 provides explicit when-to-use guidance: 'Use after listing a new property to find potential buyers in the existing lead database.' It also names specific alternatives for reverse matching and ranked matching, making it clear when this tool is preferred versus the alternatives.

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