qobrix_get_lead_properties

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

No annotations are present, so the description itself discloses behavior. It explains that the tool returns properties attached to an opportunity in the canonical RESO Demand/Solution matching pattern, and clarifies that it is the demand-side matching tool. It doesn't cover edge behaviors like pagination or auth, but for a simple read operation this is acceptable.

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 longer than one sentence but is well-structured: main purpose, then use-case context, alternatives, stage, and parameter clarification. Every sentence adds value, though it could be tightened slightly.

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 a single parameter, no output schema, and no annotations, the description is remarkably complete. It explains what the tool does, when to use it, what the id refers to, and how it fits into the broader process. An agent should be able to select and invoke this tool correctly.

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 input schema defines 'id' as 'Opportunity/Lead UUID', which is ambiguous. The description adds precision: 'The id is the Opportunity UUID.' This resolves the ambiguity and adds meaning beyond the schema.

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 opens with 'Get properties linked to a lead' which is a clear verb+resource+scope. It further explains the purpose by answering 'What properties does this buyer want?' and distinguishes from the reverse tool qobrix_get_leads_by_property. However, the sibling qobrix_get_properties_by_lead is not mentioned, which could cause ambiguity.

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 explicitly states when to use this tool: at the Solution/Viewing stage of the buyer journey, and contrasts it with alternatives: for free-language/ranked demand→supply, use qobrix_search_properties/qobrix_search_projects; the reverse operation is qobrix_get_leads_by_property. This gives clear when/when-not guidance.

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