list_families

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

With no annotations, the description carries the full burden. It discloses it lists family accounts but omits pagination behavior (skip/take parameters present), read-only nature, authorization needs, or response structure. Key behavioral traits are missing.

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 very concise with two sentences, front-loading the core purpose. The 'Use when' section is helpful. It could be more structured (e.g., bullet points) but avoids unnecessary text.

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 3 parameters (including pagination), no annotations, and sibling tools, the description is incomplete. It lacks explanation of pagination, ordering, or how it differs from list_members. The presence of an output schema reduces the burden slightly, but behavioral gaps remain.

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 0%, so the description should explain parameters. It does not mention skip or take, though the example 'west location' hints at location_id. The parameter titles in the schema provide some meaning, but the description adds minimal value.

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 lists family accounts and defines what a family is (linked members under a primary contact). It distinguishes from get_family (singular) by implying multiple, but does not explicitly differentiate from other list tools.

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 'Use when' section provides example queries ('list all families', 'find family accounts at our west location'), implying filtering by location. However, no explicit guidance on when not to use (e.g., when a specific family is needed via get_family) or alternatives is given.

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