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

Goes well beyond the annotations by explaining the matching service mechanics: it is free, surfaces a few providers with availability that accept the family's insurance, spares the family from calling anyone, and returns a private confirmation link. This describes the practical outcome of the call, which readOnlyHint/idempotentHint alone would not convey; the family-initiated confirmation at the link keeps it consistent with readOnlyHint=true.

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 tight sentences, front-loaded with the resource and coverage scope before the usage cue and return behavior. Every sentence carries information, though the care-type enumeration is partially redundant with the enum schema descriptions.

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?

For a read-only matching tool with no output schema, the description supplies geography (US), coverage scope, trigger conditions, and the return value (a private link), which is exactly what an agent needs to set expectations. Nothing material is missing for correct 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 every parameter is already documented, including the care_types enum values. The description only restates the care type vocabulary and adds no extra semantics (e.g., how zip vs. state interact, or what happens when insurance is omitted), so the baseline of 3 applies.

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?

States a specific verb and resource ('Find special needs care in the US') and immediately enumerates the four covered care types (ABA, special needs schools, speech therapy, diagnostic testing). This makes it easy to separate from the sibling tools, which concern cost estimation and IEP goals rather than provider matching.

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 trigger conditions: 'Use when someone asks for help finding care, a provider that takes their insurance, or a special needs school near them.' It lacks explicit when-not guidance and never routes the agent to get_aba_therapy_cost for pricing questions, so it falls short of a 5.

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