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

Annotations already declare readOnlyHint=true, destructivHint=false and openWorldHint=true, so the safety profile is covered. The description adds the returned field set, which is genuine value, but says nothing about pagination behavior, total counts, or whether archived families are included — the most consequential ambiguity for a list endpoint.

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 sentences: the first front-loads purpose and the returned field inventory, the second covers filtering and the endpoint path. Dense but no filler; the field enumeration is long yet arguably earns its place given there is no output schema.

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?

With no output schema, describing the returned fields is exactly the right compensation, and annotations cover safety. The remaining gap is whether archived/soft-deleted families appear in results and how pagination interacts with a total count, which matters for a list endpoint with 7 optional filters.

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 schema already documents all seven parameters including cross-references to jackrabbit_list_options for status_id and location_id. The description's filter list mirrors the schema without adding format, matching semantics, or interaction rules (e.g., whether filters AND together). Baseline 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 ('List family accounts (billing households)'), clarifies the business meaning of 'family' as a billing household, and enumerates what comes back. It doesn't distinguish itself from siblings like jackrabbit_get_family or jackrabbit_list_archived_families, but an agent can tell broadly what it does.

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?

The filter enumeration ('Filter by status, location, name, phone or last update') implies when to reach for this tool, but there is no explicit guidance on when to prefer it over jackrabbit_list_archived_families or to fetch a single record via jackrabbit_get_family. Usage is inferable but not stated.

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