qobrix_get_properties_by_lead

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

With no annotations, the description carries the full burden. It adds meaningful context: the demand-side scope, explicit linking, and that the parameter is the Opportunity UUID (not property UUID). While it doesn't describe return format or rate limits, it provides substantive behavioral context for a read operation, going beyond a bare statement.

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?

Four sentences, front-loaded with the core purpose, followed by scope clarification, usage context, and alternatives. Every sentence earns its place with no redundancy or filler.

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 the tool's moderate complexity, no output schema, and no annotations, the description is thorough: it covers purpose, id semantics, usage timing, and alternatives. It doesn't detail return structure, but for a list-like read tool, the description provides sufficient context for an agent to select and invoke it 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?

Schema coverage is 100%, so baseline is 3. The description adds crucial meaning beyond the schema by clarifying that 'id' is the Opportunity UUID (not a property UUID) and framing its use in the buyer journey. This extra semantic value justifies a 4.

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 'get properties explicitly linked to a lead' with a specific resource and scope. It further differentiates by labeling it the 'demand-side view' and clarifies that the id is an Opportunity UUID, not a property UUID, which distinguishes it from similarly named siblings.

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?

Provides explicit when-to-use guidance ('after Qualification, use this to review Solution/Viewing candidates') and names concrete alternatives: qobrix_get_opportunity with include=['Properties'] and qobrix_get_leads_by_property for the reverse match. This meets the highest bar for usage guidance.

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