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

No contradiction with annotations; readOnlyHint, idempotentHint, and destructiveHint already cover the safety profile. The description adds that this returns a detailed single household entity, but does not disclose behavior for invalid IDs, missing data, or related entities. With annotations present, it is adequate but minimal.

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 concise and front-loaded with the essential idea: one household entity in detail. No words are wasted, though it could be slightly more informative without harming 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?

This is a simple one-parameter read operation with an output schema and safety annotations, so the definition is nearly sufficient. However, it leaves ambiguity about what a 'household entity' is and whether entity_id comes from list_households, list_family, or another source. An agent can probably call it correctly but with some uncertainty.

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 description does not define entity_id's format, origin, or meaning beyond 'household entity.' Since the schema provides no parameter documentation, the description should compensate but does not.

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 names the resource ('one household entity') and indicates the level of detail ('in detail'), while the title supplies the verb 'Get'. The function is clear, though it does not explicitly differentiate itself from sibling get_* tools beyond the resource name.

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 description gives no guidance on when to use this tool versus alternatives such as list_households, list_family, or other get_* tools. There is no when-to-use context, no exclusion, and no mention of where entity_id should come from.

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