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

Annotations declare destructive=true and idempotent=true, and the description adds substantive consequence detail beyond them: shared pantry, diary entries and shared cookbooks stay with the household, the departing user gets an empty pantry but keeps their own diary entries, and the household is dissolved when the last member leaves. It also correctly adds a user-confirmation requirement for a destructive zero-param call.

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?

Data-consequence information is front-loaded (what stays, what is lost, what happens to the household) with no filler sentences. The quoted intent list ("for 'leave the household', 'stop sharing my kitchen'") is slightly awkward in phrasing but earns its place as a routing trigger.

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?

Annotations cover safety and idempotency, an output schema exists, and the description covers data loss, household dissolution, and the confirmation requirement — everything needed to call correctly. The only missing piece is disambiguation from the remove_from_household sibling in a 32-tool set where both mutate membership.

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?

Zero parameters, so there is nothing to disambiguate; the baseline applies. No parameter text is needed or present.

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?

Specific verb + resource ("take the user out of their household") with concrete user-intent phrasings ("stop sharing my kitchen"). It does not distinguish itself from the sibling remove_from_household, which is the most plausible confusion (leaving oneself vs. removing someone else).

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?

Gives explicit intent triggers that select this tool and a hard prerequisite ("Confirm with the user before calling"). It lacks an explicit when-not or a pointer to remove_from_household as the alternative, which is the one routing decision an agent could get wrong here.

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