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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint=false, so the 'Read-only' sentence adds nothing. The genuinely useful disclosure beyond the structured fields is the implicit default filter: results are scoped to open items unless status is passed, which an agent cannot infer from the schema since status has no declared default.

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?

Two tight sentences with the core purpose front-loaded and the parameter guidance following in a logical order. The trailing 'Read-only' is redundant with the annotations and could be dropped, a minor waste rather than a structural problem.

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?

For a simple, non-destructive list tool with three optional parameters and no output schema, the description covers what it returns conceptually (open items across three kinds) and how the two filtering parameters behave. The only omission is the limit/pagination behavior, which is a modest gap given the schema supplies bounds and a default.

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%, so the description must carry the load; it explains the meaning and effect of status (default vs. history inspection) and kind (filtering), but says nothing about limit, whose default of 20 and maximum of 50 are only in the schema. Two of three parameters are covered, leaving a real gap for a low-coverage schema.

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 gives a specific verb and resource ('List the household's currently-open items') and immediately defines the domain with concrete examples (open questions, pending decisions, follow-ups). It does not name any sibling tool as an alternative, so the differentiation from list_decisions or list_tasks is left implicit, keeping it short of a 5.

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?

It states the default behavior (open items only) and gives explicit conditions for the two optional parameters: use status for resolved/dismissed history, use kind to filter. It never names an alternative tool or says when not to use this one, so the routing guidance is clear but not complete.

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