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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds no behavioral context beyond the vague 'people and structures' scope and does not explain how the optional household_id affects behavior.

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 brief and front-loaded with the core subject, but it is under-specified rather than efficiently complete. It provides no verb or usage context, so brevity comes at the cost of clarity.

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?

Despite the simple schema and helpful annotations, the description omits the relationship between 'family' and 'household' and any selection semantics for household_id. An agent cannot reliably determine whether to pass the parameter or what the output scope will be, so the description is not complete enough for trustworthy 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 0%, and the sole parameter household_id is not mentioned in the description. The phrase 'people and structures' does not clarify what household_id selects, whether it is optional, or what an empty call returns, so the description fails to compensate for the schema's lack of documentation.

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 identifies the resource as 'Household entities — people and structures,' which conveys what the tool returns, but it lacks an explicit verb like 'list' or 'retrieve.' It also does not distinguish this from the sibling tool list_households, so scope remains ambiguous.

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?

There is no guidance on when to use this tool versus list_households, list_accounts, or get_household_aum. The description is a fragment with no context, condition, alternative, or exclusion, leaving usage entirely to inference.

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