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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so safety is covered. The description adds real behavioral context beyond them: the ~25-result cap on active listings, the returned fields, click-through to the backpr.com finder page, named data sources with licenses, and the home-based exclusion. It does not discuss pagination, rate limits or permissions, so it is not exhaustive.

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?

Front-loaded with purpose, then scope, then return shape, then caveats — every sentence carries information. It is slightly long and the closing disclaimer ('A listing isn't an endorsement') is more legal framing than invocation guidance, keeping it just below a 5.

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?

An output schema exists, so return values need not be spelled out, yet the description still summarizes them briefly. Scope rules, exclusions, precedence, and the result cap are all present — nothing an agent needs to invoke this correctly is missing.

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 nonetheless adds the cross-parameter precedence rule ('ZIP wins if both are given') and clarifies 'optionally by program type', which the schema cannot express. It does not restate the field-level formats, which the schema already handles.

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+resource ('Find childcare centers, school-age programs, camps and youth programs') and pins down the source (BackPR's program finder, official state/local licensing data). It is clearly distinct from the generic search_backpr sibling, so an agent can route correctly without opening a schema.

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?

Gives concrete conditions: search one state by city or 5-digit ZIP, optionally filter by program type, and states the ZIP-over-city precedence rule. It also states a clear exclusion (home-based family childcare is never listed). It does not compare itself to any sibling tool by name, so it stops 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.