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

Annotations already indicate readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds no behavioral context beyond entity composition; it does not mention filtering semantics, default behavior when household_id is omitted, or what happens if no matches exist.

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 extremely brief and easy to parse, but it is a fragment rather than a structured explanation. It earns brevity points while sacrificing the substance needed to make the tool self-describing.

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?

The tool is simple and has an output schema, but the description omits parameter behavior and any decision guidance relative to sibling list tools. The combination of a 0% param coverage schema and a two-word description leaves meaningful gaps for an agent selecting or invoking the tool.

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%, yet the description does not mention household_id or how it affects the result. With a single parameter and no compensating explanation, an agent cannot confidently determine what value to supply or what an omitted value means.

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 clarifies that 'family' means household entities and enumerates their composition ('people and structures'), which adds meaning beyond the title. However, it is a noun phrase rather than a statement of what the tool does, and it does not clearly distinguish this operation from siblings like list_households or list_facilities.

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?

No guidance is given for when to use this tool versus alternatives such as list_households, list_facilities, or list_accounts. The description provides no context about typical use cases, prerequisites, or situations where another sibling would be more appropriate.

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