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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds useful context (aggregated multi-type feed, newest-first ordering, household expansion) but says nothing about pagination behavior or the offset/limit implications despite skip/take existing.

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 zero waste: content and ordering are front-loaded, the household case follows, and the API path is a compact trailing reference.

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?

No output schema exists, but the description names the returned item types and ordering, and the schema fully documents pagination. For a read-only, three-parameter tool this is largely complete, though return-shape detail (e.g. pagination limits on results) is not addressed.

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 100%, so constituent_id, skip and take are already documented, giving a baseline of 3. The description adds genuine meaning beyond the schema by explaining that a household Id expands to every member's timeline, which the schema's parenthetical does not fully convey.

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+resource ('activity timeline for a constituent') and enumerates the content types it aggregates (gifts, interactions, notes, tasks), which implicitly separates it from the single-entity list siblings. It does not, however, explicitly name an alternative such as bloomerang_list_interactions, so the differentiation is inferred rather than stated.

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 one conditional usage note — pass a household Id to get every member's timeline — but offers no when-to-use vs when-to-use-something-else guidance relative to the many list/get siblings. Usage is implied by the resource rather than explicitly scoped.

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