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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered structurally. The description adds genuinely new behavioral context: the 'first names only' privacy constraint on returned identity data. It stops short of covering pagination or error behavior, but that is a modest gap against rich annotations.

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?

A single dense sentence with the resource named first and the returned fields front-loaded, ending with the 'Read-only' qualifier. Efficient with no filler, though the em-dash enumeration is long enough that it reads more as a field dump than a tightly prioritized statement.

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?

An output schema exists, so the description need not explain return values, yet it usefully previews the returned fields. The one parameter is fully documented in the schema and the safety traits are covered by annotations, leaving nothing an agent needs missing to call it correctly.

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 100% for the single optional 'household' parameter, so the schema already explains the name-or-id format and the omit-when-single case. The description only implies the household context via its opening phrase and adds no syntax or format detail. Baseline 3 is appropriate.

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?

States a specific resource (the household's chores) and enumerates exactly what it returns: due/overdue items, turn ownership, who took/did it last, and the person's own chores. This distinguishes it cleanly from siblings like read_dinners, read_shopping_list, and the write-side mark_chore_done.

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?

Usage is implied by the content enumeration and the 'Read-only' tag, but there is no explicit when-to-use statement, no mention of the complementary sibling mark_chore_done, and no conditions or exclusions. An agent can infer intent but is given no routing guidance.

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