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

Description aligns with annotations (readOnlyHint, openWorldHint) and adds behavioral details: ranking by un-buyable score, free-text matching fields, and city scope. No contradictions.

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 with zero fluff. The most critical information (what, where, how, options) is 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?

Covers purpose, filtering, and ranking. Lacks explicit mention of return format or fields, which would be helpful given no output schema, but the description is still sufficient for basic usage.

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 covers all 4 parameters with descriptions. Description adds semantic value by clarifying that free-text query matches business name, description, and review text, and that city must be a launched HomeClip city.

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?

Description specifies a clear action ('Find'), a specific resource ('verified home-services contractors'), and a unique differentiator ('ranked by an un-buyable Trust Score'). It distinguishes from siblings like 'get_pro' (single pro) and 'list_association_members' (associations).

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 context on when to use (launched cities, with optional filters) and what the query matches. Does not explicitly state when not to use or name alternatives, but the sibling list implies distinct use cases.

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