List Households Events Notifications

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

No annotations are provided, so the description carries the full burden of behavioral disclosure, and 'Get All' discloses almost nothing. It does not mention that pagination applies (despite page, perPage, and paginationSeed parameters), what default ordering is, or that results can be filtered. It conveys only the minimal fact that this is a read/list operation.

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?

'Get All' is extremely short, but this is under-specification rather than earned conciseness. A two-word phrase that merely restates the operation name cannot be credited with front-loading useful information, since no information is actually conveyed.

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 tool with 8 parameters, no annotations, and 0% schema coverage, the description is completely inadequate. It omits what a household event notification is, how pagination works, what filtering/ordering options do, and the scope of the returned data. The presence of an output schema only covers return structure, leaving all usage context unexplained.

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% — none of the 8 parameters (page, perPage, orderBy, orderDirection, queryFilter, paginationSeed, accept-language, orderByNullPosition) are described in the schema. The description adds nothing about any of these parameters, leaving pagination, sorting, and filtering semantics completely undocumented. With coverage this low, the description was required to compensate and did not.

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 is the two-word phrase 'Get All', which merely restates the list operation already implied by the tool name and title; it is a tautology. It names no specific resource and adds nothing beyond 'retrieve everything'. It also fails to distinguish this listing tool from the sibling get_households_events_notifications_by_item, which retrieves a single item.

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 is given for when to use this tool versus the sibling CRUD tools on the same resource. There is no mention of choosing list over get_households_events_notifications_by_item, nor any note about pagination being needed for large result sets. The description provides zero context for tool selection.

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