Search Provider Directory

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

Annotations already declare read-only and idempotent. The description adds value by detailing pagination (page, per_page) and specifying the exact fields returned. It does not mention any destructive or authentication requirements, but those are covered by annotations. A small omission is lack of mention about result ordering or completeness.

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 four sentences, front-loaded with purpose and return fields. It efficiently separates usage guidance and sibling differentiation. No unnecessary words.

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 complexity (8 params, 1 required) and rich annotations, the description covers the main purpose, output fields, and sibling relationships. It lacks explicit mention of error conditions or ordering, but these are not critical for a browse tool. Overall, it is sufficiently complete for an AI agent to understand selection and invocation.

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 description coverage is 100%, so the baseline is 3. The description mentions some parameters (category, location, min_rating) and ties per_page and page to pagination, but adds little extra meaning beyond what the schema already provides. No additional context for tier1_grade or practice_size_fit.

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 is a 'paginated browse of the healthcare service provider directory' with specific filters (category, location, minimum quality score) and lists return fields. It also distinguishes from siblings by directing to match_practice for scored recommendations and to get_provider_detail for full profiles.

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 states when to use this tool ('open-ended exploration and filtering') and when not to ('for scored recommendations to a specific practice profile, use match_practice instead'). Also advises passing a returned slug to get_provider_detail.

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