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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds useful authorization context (visibility is scoped to the acting household member). It omits ordering, default page size, and whether the 'before' cursor walks backwards until exhausted.

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 front-loaded sentence with no filler. It is arguably too terse rather than too long, but there is no structural waste.

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?

With no output schema, undocumented limit and conversation_id semantics, and no statement of ordering or how paging terminates, the definition leaves real gaps for a paginated read tool. A sentence on ordering and the limit default would close most of them.

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 coverage is only 33% -- just the 'before' cursor is documented in the schema, and the description adds nothing about conversation_id, limit, or the maximum of 500. The description does not compensate for the undocumented parameters.

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 verb and resource (read messages from a conversation) and adds an authorization scope ('visible to the acting household member'). It is distinguishable from list_conversations, though it doesn't explicitly contrast with it or with get_activity_feed.

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?

No guidance on when to use this versus list_conversations or get_activity_feed, and no preconditions stated. The word 'recent' hints at a reverse-chronological read but the caller must infer pagination strategy entirely from the schema.

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